RE: [Sip] RFC 3608 on Session Initiation Protocol (SIP) Extension Header Field for Service Route Discovery During Registration

Hi Chris,

Let me make a brief excursion to the history of Service-Route: I remember
some discussions concerning the possible usage of an option-tag for
(P-)Service-Route in the early stage of the I/D. At that time the working
assumption was, that this would be a P-header field
(i.e. P-Service-Route). Since you cannot Require a P-header field, the
discussion immediately ended at that time.

Lateron working assumption was changed: the P-header field was changed to
a normal header field. But nobody has brought up again a requirement
for an option-tag service-route.

In case such a requirement turns out be useful, we could consider to make
an additional document describing the Require/Supported behavior with
Service-Route.

What is your main motivation for such an option-tag for service-route?

cheers,
 Bernie

On Thu, 9 Oct 2003, Chris Boulton wrote:

> Dean, Bernie,
>
> This may seem a silly question (I'm sure I will be told that it is ;-),
> BUT I was wondering why the use of the 'Supported/Require' headers are
> not required with this extension.
>
> Regards,
>
> Chris.
>
>
> >-----Original Message-----
> >From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]
> >Sent: 09 October 2003 01:01
> >Cc: rfc-editor@rfc-editor.org; sip@ietf.org
> >Subject: [Sip] RFC 3608 on Session Initiation Protocol (SIP) Extension
> >Header Field for Service Route Discovery During Registration
> >
> >
> >A new Request for Comments is now available in online RFC libraries.
> >
> >
> >        RFC 3608
> >
> >        Title:      Session Initiation Protocol (SIP) Extension Header
> >                    Field for Service Route Discovery During
> >                    Registration
> >        Author(s):  D. Willis, B. Hoeneisen
> >        Status:     Standards Track
> >        Date:       October 2003
> >        Mailbox:    dean.willis@softarmor.com, hoeneisen@switch.ch
> >        Pages:      17
> >        Characters: 35628
> >        Updates/Obsoletes/SeeAlso:    None
> >
> >        I-D Tag:    draft-ietf-sip-scvrtdisco-04.txt
> >
> >        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3608.txt
> >
>
>
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use sip-implementors@cs.columbia.edu for questions on current sip
> Use sipping@ietf.org for new developments on the application of sip
>

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip