Skip to main content
Datatracker
Groups
By area/parent
Apps & Realtime
General
Internet
Ops & Management
Routing
Security
Web and Internet Transport
IAB
IRTF
IETF LLC
RFC Editor
Other
Active AGs
Active Areas
Active Directorates
Active IAB Workshops
Active Programs
Active RAGs
Active Teams
New work
Chartering groups
BOFs
BOF Requests
Other groups
Concluded groups
Non-WG lists
Documents
Search
Recent I-Ds
I-D submission
IESG dashboard
RFC streams
IAB
IRTF
ISE
Editorial
Subseries
STD
BCP
FYI
Meetings
Agenda
Materials
Floor plan
Registration
Important dates
Request a session
Session requests
Upcoming meetings
Upcoming meetings
Past meetings
Past meetings
Meeting proceedings
Other
IPR disclosures
Liaison statements
IESG agenda
NomComs
Downref registry
Statistics
I-Ds/RFCs
Meetings
API Help
Release notes
Report a bug
User
Sign in
Password reset
Preferences
New account
Report a bug
Sign in
Javascript disabled?
Like other modern websites, the IETF Datatracker relies on Javascript. Please enable Javascript for full functionality.
Best Practice to map HTTP to COAP and viceversa
draft-castellani-core-http-coap-mapping-01
Status
Email expansions
History
Approval announcement
Draft
of message to be sent
after
approval:
Announcement
Ballot Text
RFC Editor Note