Re: [sipcore] H-I in 100 response (was REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis)

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Wed, 03 November 2010 10:42 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2DA43A68F9 for <sipcore@core3.amsl.com>; Wed, 3 Nov 2010 03:42:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.249
X-Spam-Level:
X-Spam-Status: No, score=-106.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bvvDPjoMiRpe for <sipcore@core3.amsl.com>; Wed, 3 Nov 2010 03:42:54 -0700 (PDT)
Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by core3.amsl.com (Postfix) with ESMTP id AE7173A68C8 for <sipcore@ietf.org>; Wed, 3 Nov 2010 03:42:53 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id oA3AcGGu012394 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 3 Nov 2010 11:42:53 +0100
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.44]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 3 Nov 2010 11:41:43 +0100
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@cisco.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Wed, 3 Nov 2010 11:41:42 +0100
Thread-Topic: [sipcore] H-I in 100 response (was REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis)
Thread-Index: Act63BKdJQ94zP/mThCiSQMb7hD1HQAZZW6g
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE2198FEEE6@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <4C69ADA8.1010802@nostrum.com> <4C753AAA.3030407@nostrum.com> <A444A0F8084434499206E78C106220CA01C4874C5F@MCHP058A.global-ad.net> <AANLkTi=Sz5ddsWVmta5N_T8JHhrSytzALQDw=kzLcQAV@mail.gmail.com> <A444A0F8084434499206E78C106220CA023554638D@MCHP058A.global-ad.net> <AANLkTikxiK2S0oQ6Q7=JkwxYNjxK3O7BBrx+sWUQ5vOB@mail.gmail.com> <A444A0F8084434499206E78C106220CA023554681D@MCHP058A.global-ad.net> <4CD08E7A.1020503@cisco.com>
In-Reply-To: <4CD08E7A.1020503@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.80
Subject: Re: [sipcore] H-I in 100 response (was REMINDER: Re: WGLC: draft-ietf-sipcore-rfc4244bis)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Nov 2010 10:42:55 -0000

Please do not put it in 100 responses, i.e. MUST NOT.

Note that if it is put in 1xx responses that are not sent reliably, then in my understanding you have no means of telling you have lost it along with the response. So in this case it would have to be repeated in the final response. However there is probably a use case for being able to inform the user of call diversion at alerting time, so I would certainly allow it, i.e. MAY to generate it or add to it, MUST to pass one on if you receive it.

Keith

> -----Original Message-----
> From: sipcore-bounces@ietf.org 
> [mailto:sipcore-bounces@ietf.org] On Behalf Of Paul Kyzivat
> Sent: Tuesday, November 02, 2010 10:20 PM
> To: sipcore@ietf.org
> Subject: Re: [sipcore] H-I in 100 response (was REMINDER: Re: 
> WGLC: draft-ietf-sipcore-rfc4244bis)
> 
> 
> 
> On 11/2/2010 4:31 PM, Elwell, John wrote:
> > So the remaining issue from this thread concerns whether to 
> mandate History-Info in a all provisional responses or just 
> non-100 provisional responses (subject to presence of the 
> option tag in the request). Given that 100 tends to be 
> generated differently from other provisional responses, and 
> given the marginal use of H-I in 100 responses, I would 
> prefer either to omit H-I from 100 responses or use MAY. I 
> don't have a strong opinion, but perhaps others have a view.
> 
> Requiring (even permitting) H-I in 100 responses is a *terrible* idea.
> 
> I don't see why you would need H-I in *any* provisional 
> responses (with the possible exception of 199.)
> 
> (Disclaimer - I have not read all the discussion on this subject.)
> 
> 	Thanks,
> 	Paul
> 
> > John
> >
> >
> >> -----Original Message-----
> >> From: Mary Barnes [mailto:mary.ietf.barnes@gmail.com]
> >> Sent: 02 November 2010 19:51
> >> To: Elwell, John
> >> Cc: sipcore@ietf.org
> >> Subject: Re: [sipcore] REMINDER: Re: WGLC:
> >> draft-ietf-sipcore-rfc4244bis
> >>
> >> John,
> >>
> >> I've done the same. A couple responses inline below [MB2].
> >>
> >> Thanks,
> >> Mary.
> >>
> >> On Tue, Nov 2, 2010 at 4:06 AM, Elwell, John 
> >> <john.elwell@siemens-enterprise.com>  wrote:
> >>> Mary,
> >>>
> >>> I have responded below, stripping out the stuff where I
> >> have nothing further to add.
> >>>
> >> <snip>
> >>>>> 2. It nearly always uses the term "header" rather than
> >>>> "header field", although never, as far as I know, meaning the 
> >>>> entire SIP header.
> >>>> [MB] I'm not sure that I fully understand the concern. Can
> >> you point
> >>>> out a specific sentence or section of concern?  The term
> >> "header" is
> >>>> used when it is referring to the History-Info header
> >> field, but that
> >>>> is done in other documents as well.  In general, I think it's 
> >>>> understood that it's referring to the header field when it's 
> >>>> qualified. Perhaps you're referring to places where it is not
> >>>> qualified?   The term hi-entry is used, as well.
> >>>> [/MB]
> >>> [JRE] I have explained in more detail in my comments on -02.
> >> [MB2] I've responded to that in my subsequent response to your 
> >> comments. [/MB2]
> >>>
> >>> <snip/>
> >>
> >>>>>
> >>>>> 18. Section 4.2.2:
> >>>>> "the UAS MUST
> >>>>>    include any History-Info received in the request  in the
> >>>> subsequent
> >>>>>    response"
> >>>>> Does this include 100 responses?
> >>>> [MB] I would think so. Can you think of a reason why it
> >> shouldn't?  I>>  would think it could be useful for debug. [/MB]
> >>> [JRE] The 100 response typically only travels back a single
> >> hop, so the benefit of H-I in a 100 is marginal. Also some 
> >> implementations might send back a 100 response quite early during 
> >> processing, perhaps even before they decide whether to act as a 
> >> proxy, a UAS or a redirect, so knowing how to populate H-I 
> in a 100 
> >> might be difficult.
> >> [MB2] If it has no additional hi-entries, then there is nothing 
> >> additional to send back, so I don't think it hurts 
> anything - I would 
> >> agree that in most cases it's of marginal value. We can 
> include it as 
> >> an exception in that sentence if you would prefer, 
> although per the 
> >> next comment, it seems that you are okay with leaving it as is.
> >> [/MB2]
> >>>
> >>> <snip/>
> >>>>>
> >>
> >>>>>
> >>>>> 26. Section 5.2:
> >>>>> "A proxy that receives a request with the "histinfo" option
> >>>> tag in the
> >>>>>    Supported header, SHOULD forward captured History-Info in
> >>>> subsequent,
> >>>>>    provisional , and final responses "
> >>>>> Does this include 100 responses?
> >>>> [MB] That's the implication of "provisional" per RFC 3261. [/MB]
> >>> [JRE] I am doubtful about the usefulness of 100. However,
> >> it is probably fairly academic, since 100 will probably have been 
> >> sent earlier. A proxy is unlikely to send a 100 after receiving a 
> >> provisional response from a downstream entity.
> >>>
> >>>>>
> >>>>> 27. Section 5.2:
> >>>>> "A proxy MAY anonymize any hi-entry whose domain 
> corresponds to a
> >>>>>    domain for which it is responsible (as per [RFC3323 ])."
> >>>>> I don't think RFC 3323 tells me how to anonymize an hi-entry.
> >>>> [MB]  RFC 3323 discusses anonymization and the role of an
> >> anonymizer,
> >>>> etc. So, I'm not clear on your concern. [/MB]
> >>> [JRE] I guess if we talked about anonymizing the URI in the
> >> hi-target-to-uri it would be clearer.
> >> [MB2] That's fine...I'll make it explicit that it's the 
> >> hi-targeted-to-uri in the hi-entry that is anonymized. [/MB2]
> >>>
> >>> <snip/>
> >>>
> >>>
> >>> John
> >>
> > _______________________________________________
> > sipcore mailing list
> > sipcore@ietf.org
> > https://www.ietf.org/mailman/listinfo/sipcore
> >
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore
>