[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] New version (-05) of the 199 draft - ready for WGLC?
- To: "Vijay K. Gurbani" <vkg at alcatel-lucent.com>, Dean Willis <dean.willis at softarmor.com>
- Subject: Re: [Sip] New version (-05) of the 199 draft - ready for WGLC?
- From: "Doken, Serhad" <sdoken at qualcomm.com>
- Date: Tue, 3 Mar 2009 09:19:20 -0800
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: SIP WG <sip at ietf.org>, Christer Holmberg <christer.holmberg at ericsson.com>
- Delivered-to: sip at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=sdoken at qualcomm.com; q=dns/txt; s=qcdkim; t=1236100779; x=1267636779; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Doken,=20Serhad"=20<sdoken at qualcomm.com>|To:=20 "Vijay=20K.=20Gurbani"=20<vkg at alcatel-lucent.com>,=0D=0A =20=20=20=20=20=20=20=20Dean=20Willis=0D=0A=09<dean.willi s at softarmor.com>|CC:=20SIP=20WG=20<sip at ietf.org>,=20Chris ter=20Holmberg=20<christer.holmberg at ericsson.com>|Date: =20Tue,=203=20Mar=202009=2009:19:20=20-0800|Subject:=20RE :=20[Sip]=20New=20version=20(-05)=20of=20the=20199=20draf t=20-=20ready=20for=20WGLC?|Thread-Topic:=20[Sip]=20New =20version=20(-05)=20of=20the=20199=20draft=20-=20ready =20for=20WGLC?|Thread-Index:=20AcmcERkM2XfWD+pFRTOJDEgmyz MkKwAEProg|Message-ID:=20<ED88AAAE8B3D764B9FD8558DE1775B6 9137EAF9587 at NASANEXMB09.na.qualcomm.com>|References:=20<C A9998CD4A020D418654FCDEF4E707DF0B2B4A29 at esealmw113.eemea. ericsson.se>=0D=0A=09<FA43087A-F2AA-442C-864C-1179CA8E9A3 4 at softarmor.com>=0D=0A=20<49AD4681.8090403 at alcatel-lucent .com>|In-Reply-To:=20<49AD4681.8090403 at alcatel-lucent.com >|Accept-Language:=20en-US|Content-Language:=20en-US |X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20text/plain=3B=20charset=3D"us-as cii"|Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5541"=3B=20a=3D"15935810"; bh=z5rzOjK03FqgLFeImBe4FjaUBQrA1Hbp8UFFT2F1fjI=; b=rRq7VJrBpsJl+ovaIbAv8yiTC1U1kpot0parXLBovt+PVenEguDUs+9a eBxHwZHlfs+zvx9ltyvZ6meLq49YdKxUD5rd5f3XvnjFvtjUgbC+ldW8T 5ohgBYNEAsr/ubG044M33MpwmqyHnFIcboPJLxIGdcgQokMQmZEI3K1P5 o=;
- In-reply-to: <49AD4681.8090403 at alcatel-lucent.com>
- List-archive: <http://www.ietf.org/mail-archive/web/sip>
- 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: <CA9998CD4A020D418654FCDEF4E707DF0B2B4A29 at esealmw113.eemea.ericsson.se> <FA43087A-F2AA-442C-864C-1179CA8E9A34 at softarmor.com> <49AD4681.8090403 at alcatel-lucent.com>
- Thread-index: AcmcERkM2XfWD+pFRTOJDEgmyzMkKwAEProg
- Thread-topic: [Sip] New version (-05) of the 199 draft - ready for WGLC?
> -----Original Message-----
> From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org] On Behalf Of
> Vijay K. Gurbani
> Sent: Tuesday, March 03, 2009 7:02 AM
> To: Dean Willis
> Cc: SIP WG; Christer Holmberg
> Subject: Re: [Sip] New version (-05) of the 199 draft - ready for WGLC?
>
> Dean Willis wrote:
> > We didn't get any real answers due to a bit of confusion between this
> > and keepalive. So, let's ask the question again.
> >
> > Is 199 ready for WGLC?
>
> Yes; it is well written (I had looked at a much earlier version
> and just re-read -06.)
>
> One question for Christer:
>
> - Does 199 carry a message/sipfrag MIME type that conveys the
> nature of the final non-2xx response? This may have been
> discussed in the past, and if so, please let me know. I
> do note that rfc3420 is specified in the draft as a normative
> reference, but it is not referred to anywhere in the body
> of the draft.
There was discussion around 199 carrying information about why the fork/dialog was terminated and sipfrag was mentioned to be used to convey that. However, later on Reason header within 199 is agreed to be used for that purpose. Hence, mention of 3420 might be obsolete by now.
Thanks,
Serhad
>
> Thanks,
>
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60566 (USA)
> Email: vkg at {alcatel-lucent.com,bell-labs.com,acm.org}
> Web: http://ect.bell-labs.com/who/vkg/
> _______________________________________________
> 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