[Technical Errata Reported] RFC3665 (4047)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The following errata report has been submitted for RFC3665,
"Session Initiation Protocol (SIP) Basic Call Flow Examples".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3665&eid=4047

--------------------------------------
Type: Technical
Reported by: Gergely Szabo <gergely.szabo@xxxxxxxxxxxx>

Section: 2.1

Original Text
-------------
   F3 REGISTER Bob -> SIP Server

   REGISTER sips:ss2.biloxi.example.com SIP/2.0
   Via: SIP/2.0/TLS client.biloxi.example.com:5061;branch=z9hG4bKnashd92
   Max-Forwards: 70
   From: Bob <sips:bob@xxxxxxxxxxxxxxxxxx>;tag=ja743ks76zlflH
   To: Bob <sips:bob@xxxxxxxxxxxxxxxxxx>
   Call-ID: 1j9FpLxk3uxtm8tn@xxxxxxxxxxxxxxxxxx
   CSeq: 2 REGISTER
   Contact: <sips:bob@xxxxxxxxxxxxxxxxxxxxxxxxx>
   Authorization: Digest username="bob", realm="atlanta.example.com"
    nonce="ea9c8e88df84f1cec4341ae6cbe5a359", opaque="",
    uri="sips:ss2.biloxi.example.com",
    response="dfe56131d1958046689d83306477ecc"
   Content-Length: 0

Corrected Text
--------------
   F3 REGISTER Bob -> SIP Server

   REGISTER sips:ss2.biloxi.example.com SIP/2.0
   Via: SIP/2.0/TLS client.biloxi.example.com:5061;branch=z9hG4bKnashd92
   Max-Forwards: 70
   From: Bob <sips:bob@xxxxxxxxxxxxxxxxxx>;tag=ja743ks76zlflH
   To: Bob <sips:bob@xxxxxxxxxxxxxxxxxx>
   Call-ID: 1j9FpLxk3uxtm8tn@xxxxxxxxxxxxxxxxxx
   CSeq: 2 REGISTER
   Contact: <sips:bob@xxxxxxxxxxxxxxxxxxxxxxxxx>
   Authorization: Digest username="bob", realm="atlanta.example.com",
    nonce="ea9c8e88df84f1cec4341ae6cbe5a359", opaque="",
    uri="sips:ss2.biloxi.example.com",
    response="dfe56131d1958046689d83306477ecc"
   Content-Length: 0

Notes
-----
A comma (,) is missing before the 'nonce' parameter of the Authorization header.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC3665 (draft-ietf-sipping-basic-call-flows-02)
--------------------------------------
Title               : Session Initiation Protocol (SIP) Basic Call Flow Examples
Publication Date    : December 2003
Author(s)           : A. Johnston, S. Donovan, R. Sparks, C. Cunningham, K. Summers
Category            : BEST CURRENT PRACTICE
Source              : Session Initiation Proposal Investigation
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP




[Index of Archives]     [IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

  Powered by Linux