[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] INFO Framework: Tags
- To: "Elwell, John" <john.elwell at siemens.com>, Christer Holmberg <christer.holmberg at ericsson.com>, "DRAGE, Keith (Keith)" <drage at alcatel-lucent.com>, Dean Willis <dean.willis at softarmor.com>, Paul Kyzivat <pkyzivat at cisco.com>
- Subject: Re: [Sip] INFO Framework: Tags
- From: Bob Penfield <BPenfield at acmepacket.com>
- Date: Fri, 21 Nov 2008 10:29:01 -0500
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: SIP List <SIP at ietf.org>
- Delivered-to: ietfarch-sip-archive at core3.amsl.com
- Delivered-to: sip at core3.amsl.com
- In-reply-to: <0D5F89FAC29E2C41B98A6A762007F5D0014839FD at GBNTHT12009MSX.gb002.siemens.net>
- List-help: <mailto:sip-request@ietf.org?subject=help>
- List-id: Session Initiation Protocol <sip.ietf.org>
- List-post: <mailto:sip@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
- References: <8BF9D1D9-DD57-47E9-AC73-3F96E1F35AEC at standardstrack.com> <0D5F89FAC29E2C41B98A6A762007F5D0014831AB at GBNTHT12009MSX.gb002.siemens.net> <5D1A7985295922448D5550C94DE2918002512FCF at DEEXC1U01.de.lucent.com> <CA9998CD4A020D418654FCDEF4E707DF05C0F98D at esealmw113.eemea.ericsson.se> <5D1A7985295922448D5550C94DE2918002513232 at DEEXC1U01.de.lucent.com> <9A2232A5-4C17-4600-82D9-679032C97555 at softarmor.com> <5D1A7985295922448D5550C94DE2918002513267 at DEEXC1U01.de.lucent.com> <5F753F1B-1FDA-4ADB-9BCA-8445D1363F40 at softarmor.com> <4925DFE5.7000700 at cisco.com> <6AA8F84D-8061-446F-A7BB-52C6163163E8 at softarmor.com> <5D1A7985295922448D5550C94DE2918002513272 at DEEXC1U01.de.lucent.com> A <CA9998CD4A020D418654FCDEF4E707DF05C0F997 at esealmw113.eemea.ericsson.se> <0D5F89FAC29E2C41B98A6A762007F5D0014836E5 at GBNTHT12009MSX.gb002.siemens.net> A <CA9998CD4A020D418654FCDEF4E707DF05C0F9A9 at esealmw113.eemea.ericsson.se>, <0D5F89FAC29E2C41B98A6A762007F5D0014839FD at GBNTHT12009MSX.gb002.siemens.net>
- Sender: sip-bounces at ietf.org
- Thread-index: AclLYgdhHbgtszVnT3KSuvzz4CQh4gAACWMgAAAOWEAAC1gCoAAQwYDwAAI4ohAABIybzA==
- Thread-topic: [Sip] INFO Framework: Tags
I agree with John. There is no compeling reason to include an option tag. An info-package that actually needs an option tag would need to be defined in a standards track document.
Keep it simple.
Less is more.
cheers,
(-:bob
________________________________________
From: sip-bounces at ietf.org [sip-bounces at ietf.org] On Behalf Of Elwell, John [john.elwell at siemens.com]
Sent: Friday, November 21, 2008 8:20 AM
To: Christer Holmberg; DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat
Cc: SIP List
Subject: Re: [Sip] INFO Framework: Tags
Christer,
OK, it might be simple, but still unnecessary, so why do it. I haven't
heard a compelling argument in its favour. Per-package option tags are
far more compelling (depending on particular needs of a package),
although I agree such packages would need a standards track document.
John
> -----Original Message-----
> From: Christer Holmberg [mailto:christer.holmberg at ericsson.com]
> Sent: 21 November 2008 12:16
> To: Elwell, John; DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat
> Cc: SIP List
> Subject: RE: [Sip] INFO Framework: Tags
>
>
> John,
>
> What is "un-simple" by defining an option tag value??? We
> have done that
> many times before...
>
> Regards,
>
> Christer
>
>
>
>
> -----Original Message-----
> From: Elwell, John [mailto:john.elwell at siemens.com]
> Sent: Friday, November 21, 2008 6:46 AM
> To: Christer Holmberg; DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat
> Cc: SIP List
> Subject: RE: [Sip] INFO Framework: Tags
>
> Christer,
>
> > -----Original Message-----
> > From: Christer Holmberg [mailto:christer.holmberg at ericsson.com]
> > Sent: 20 November 2008 22:53
> > To: DRAGE, Keith (Keith); Dean Willis; Paul Kyzivat
> > Cc: SIP List; Elwell, John
> > Subject: RE: [Sip] INFO Framework: Tags
> >
> >
> > Hi,
> >
> > I still think we shall have an option tag for the extension itself.
> >
> > Eventhough it does not gurantee that the UAS supports specific info
> > packages, at least you can use it to help finding a UAS
> which supports
>
> > the extensions (by using the sip.extensions feature tag).
> [JRE] I haven't heard a compelling argument for this. Keep it simple.
>
> >
> > And, as Dean said, it can be used with OPTIONS.
> [JRE] And I haven't heard a compelling argument for this. Keep it
> simple.
>
> John
>
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip