RFC 4975, "The Message Session Relay Protocol (MSRP)", September 2007

Note: This RFC has been updated by RFC 7977, RFC 8591, RFC 8873, RFC 8996

Errata ID: 1280
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-14
Held for Document Update by: Robert Sparks

Section 7.1.1,p.19 says:

<<<  at the end of the (indented) second paragraph  >>
 
        [...]  For example, an endpoint could concatenate an instance
      identifier such as a MAC address, its idea of the number of
      seconds since the epoch, a process ID, and a monotonically
      increasing 16-bit integer, all base-64 encoded.  Alternately, an
      endpoint without an on-board clock could simply use a 64-bit
      random number.

It should say:

 
        [...]  For example, an endpoint could concatenate an instance
      identifier such as a MAC address, its idea of the number of
      seconds since the epoch, a process ID, and a monotonically
      increasing 16-bit integer, all base-64 encoded.  Alternately, an   
      endpoint without an on-board clock could simply use a 64-bit
|     random number and base-64 encode it.

Notes:

Clarification; otherwise, "Alternately" could be grossly misunderstood
to indicate a direct alternative for the header field value.

Report New Errata