RFC 6442, "Location Conveyance for the Session Initiation Protocol", December 2011

Note: This RFC has been updated by RFC 8262, RFC 8787

Errata ID: 5027
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Larry Reeder
Date Reported: 2017-05-31
Verifier Name: Ben Campbell
Date Verified: 2018-01-25

Section 5.1 says:

 --boundary1

   Content-Type: application/pidf+xml
   Content-ID: <target123@atlanta.example.com>
   <?xml version="1.0" encoding="UTF-8"?>
       <presence

It should say:

 --boundary1

   Content-Type: application/pidf+xml
   Content-ID: <target123@atlanta.example.com>

   <?xml version="1.0" encoding="UTF-8"?>
       <presence

Notes:

The PIDF-LO examples in RFC 6442 don't have an empty line between the message headers and the message body in the pidf+xml bodies.

RFC 2046, section 5.1 says this about multipart MIME body parts: " After its boundary delimiter line, each body part then consists of a header area, a blank line, and a body area".

This errata also applies to the example in section 5.2

Report New Errata