Re: [sipcore] [Technical Errata Reported] RFC5002 (4649)

Brett Tate <brett@broadsoft.com> Thu, 31 March 2016 11:35 UTC

From: Brett Tate <brett@broadsoft.com>
References: <20160329145448.53405180004@rfc-editor.org> 5ee96ec3f7f636b401ca1132aabf95c3@mail.gmail.com
In-Reply-To: 5ee96ec3f7f636b401ca1132aabf95c3@mail.gmail.com
MIME-Version: 1.0
Thread-Index: AQLWkLUImq/GIANv3gUjVXOWVpZox51mdRlAgALrvkA=
Date: Thu, 31 Mar 2016 07:35:47 -0400
Message-ID: <f372616b1f2bed6c0f46bce87e3807ce@mail.gmail.com>
To: sipcore@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/sipcore/BhTBkFqxuaHZzvXTW7Sx9XtDI04>
Cc: German.Blanco@ericsson.com, iesg@ietf.org, Gonzalo.Camarillo@ericsson.com, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [sipcore] [Technical Errata Reported] RFC5002 (4649)
Precedence: list

Copying sipcore since similar errata being discussed.

> -----Original Message-----
> From: Brett Tate [mailto:brett@broadsoft.com]
> Sent: Tuesday, March 29, 2016 10:59 AM
> To: 'RFC Errata System'; 'Gonzalo.Camarillo@ericsson.com';
> 'German.Blanco@ericsson.com'; 'iesg@ietf.org'
> Subject: RE: [Technical Errata Reported] RFC5002 (4649)
>
> Hi,
>
> My proposed resolution is similar to what occurred within RFC 3325
errata
> (3744 and 3894).
>
> > -----Original Message-----
> > From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> > Sent: Tuesday, March 29, 2016 10:55 AM
> > To: Gonzalo.Camarillo@ericsson.com; German.Blanco@ericsson.com;
> > iesg@ietf.org
> > Cc: brett@broadsoft.com; rfc-editor@rfc-editor.org
> > Subject: [Technical Errata Reported] RFC5002 (4649)
> >
> > The following errata report has been submitted for RFC5002, "The
> > Session Initiation Protocol (SIP) P-Profile-Key Private Header
(P-Header)".
> >
> > --------------------------------------
> > You may review the report below and at:
> > http://www.rfc-editor.org/errata_search.php?rfc=5002&eid=4649
> >
> > --------------------------------------
> > Type: Technical
> > Reported by: Brett Tate <brett@broadsoft.com>
> >
> > Section: 5
> >
> > Original Text
> > -------------
> > The following is an example of a P-Profile-Key header field that
> > contains a Wildcarded Public Service Identity:
> >
> > Corrected Text
> > --------------
> > If the URI contains a comma, question mark or semicolon, the URI MUST
> > be enclosed in angle brackets (< and >).
> >
> > The following is an example of a P-Profile-Key header field that
> > contains a Wildcarded Public Service Identity:
> >
> > Notes
> > -----
> > If addr-spec is used when there are parameters, it is ambiguous if the
> > parameters are URI parameters or header parameters.  For consistency
> > with RFC
> > 3261 section 20, the same bracket rule is indicated even if comma and
> > question mark do not cause an issue.
> >
> > Instructions:
> > -------------
> > This erratum 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.
> >
> > --------------------------------------
> > RFC5002 (draft-camarillo-sipping-profile-key-02)
> > --------------------------------------
> > Title               : The Session Initiation Protocol (SIP)
P-Profile-Key
> > Private Header (P-Header)
> > Publication Date    : August 2007
> > Author(s)           : G. Camarillo, G. Blanco
> > Category            : INFORMATIONAL
> > Source              : IETF - NON WORKING GROUP
> > Area                : N/A
> > Stream              : IETF
> > Verifying Party     : IESG

Re: [sipcore] [Technical Errata Reported] RFC5002… Brett Tate