Re: [sipcore] WGLC: draft-ietf-sipcore-rfc4244bis

Cullen Jennings <> Tue, 21 June 2011 23:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 5349821F853A for <>; Tue, 21 Jun 2011 16:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.592
X-Spam-Status: No, score=-110.592 tagged_above=-999 required=5 tests=[AWL=0.007, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id C0R6BnBdrKSZ for <>; Tue, 21 Jun 2011 16:09:07 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id CBBE521F8528 for <>; Tue, 21 Jun 2011 16:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=3194; q=dns/txt; s=iport; t=1308697735; x=1309907335; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=aD8fiiiy51MMGx6QIYXNtxGG/kojXx1YO8GohQszb2E=; b=j7uww7YnwnmixO0N51e5SQQoGvaIxsjgtj3G+yvsxXQrWZtZiV8OHnk1 Si+YOkwKmrTSfDypnmCEN14P3KQpBFrIQEmLUu47fDx2oj+58ZMIID+Oe 7ycxBsszIXLJHF/Xh21s2hlEJS9WfXpwF3dMEg/ZbWqPOaLEnrtVjZScC o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAHEjAU6rRDoJ/2dsb2JhbABUpwZ3qkmeIIYqBIciikSQJg
X-IronPort-AV: E=Sophos;i="4.65,403,1304294400"; d="scan'208";a="466588470"
Received: from ([]) by with ESMTP; 21 Jun 2011 23:08:55 +0000
Received: from ( []) by (8.14.3/8.14.3) with ESMTP id p5LN8t6D002944; Tue, 21 Jun 2011 23:08:55 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Cullen Jennings <>
In-Reply-To: <>
Date: Tue, 21 Jun 2011 16:08:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <>
To: " WG" <>
X-Mailer: Apple Mail (2.1084)
Subject: Re: [sipcore] WGLC: draft-ietf-sipcore-rfc4244bis
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 21 Jun 2011 23:09:08 -0000

Privacy issue: There is no way to know that the next downstream proxy support the processing required by the privacy header. 

What's this for: The most concrete use is making sure a call arriving at a voice mail servers goes to the correct mailbox. However, the draft is woefully underspecified to be able to implement this from the draft. This draft specifies a bunch of data that can get dumped in a bag, but to allow interoperable implementation, it needs to say how one could use that data for some actually feature. 

As a coauthor of 4244, I agree this draft is better than 4244 but I don't think it is ready to publish.Given what we have learned about 4244 since it was published, I would support 4244 being changed to historic. 

Does it work? Consider text such as  

       Note, this would be
       the original AoR if all the entities involved support the
       History-info header field and there is absence of an "mp" header
       field parameter prior to the "rc" header field parameter in the
       hi-target-param in the History-info header field.  However, there
       is no guarantee that all entities will support History-Info, thus
       the hi-entry that matches the value of the "rc" parameter of the
       first hi-entry with an "rc" parameter in the hi-target-param
       within the domain associated with the target URI at the
       destination is more likely to be useful.

This amounts to you might some information you want at X but then again you might not. The whole draft is like this - it's pretty hard to imagine this will reliably work for nearly any purpose I can think of given the limitations of the draft. 

Backwards Compatibly - yes the syntax is backwards compatible but no effort has been put into consider what would happen if some elements in the network were doing 4244 and some where doing 4244bis.

Implementations: I'd like to know about implementations that were going to use this data. And by use, I don't mean write to the history header but instead ones that are going to read from it and use the information for some purpose. 

Does not meet requirements. As far as I can tell, the draft does not meet the requirements outline in section A.1 of the draft. 

On Jun 5, 2011, at 17:33 , Paul Kyzivat wrote:

> [as co-chair]
> The current editor of draft-ietf-sipcore-rfc4244bis believes that the document has no remaining technical issues, and is ready for evaluation. Today, we are starting a two-week working group last call period. This last call period ends on Sunday, June 19.
> The latest version of the document can be retrieved here:
> Any comments on the document should be sent to the SIPCORE mailing list.
>     Thanks,
>     Paul
> _______________________________________________
> sipcore mailing list

Cullen Jennings
For corporate legal information go to: