Re: [Insipid] Next version of the backwards compatibility proposal

Paul Kyzivat <pkyzivat@alum.mit.edu> Fri, 25 October 2013 15:36 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0E411E832E for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 08:36:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.304
X-Spam-Level:
X-Spam-Status: No, score=-0.304 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RpibHhAkRfUb for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 08:36:53 -0700 (PDT)
Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by ietfa.amsl.com (Postfix) with ESMTP id 3D28C11E8329 for <insipid@ietf.org>; Fri, 25 Oct 2013 08:36:12 -0700 (PDT)
Received: from omta17.westchester.pa.mail.comcast.net ([76.96.62.89]) by QMTA11.westchester.pa.mail.comcast.net with comcast id hP3c1m0071vXlb85BTc7nJ; Fri, 25 Oct 2013 15:36:07 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta17.westchester.pa.mail.comcast.net with comcast id hTc71m00P3ZTu2S3dTc7dJ; Fri, 25 Oct 2013 15:36:07 +0000
Message-ID: <526A8FE7.3070203@alum.mit.edu>
Date: Fri, 25 Oct 2013 11:36:07 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.0.1
MIME-Version: 1.0
To: insipid@ietf.org
References: <201310242226.r9OMQ2Pv004316@rcdn-core2-1.cisco.com>
In-Reply-To: <201310242226.r9OMQ2Pv004316@rcdn-core2-1.cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1382715367; bh=SBAlMJMaWjofesk4VTrZAGL7twKzNTNXo3dgzaGAi18=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=m/OMTuvgJhMhMGa0N1xJ4qXWE2lLRqU++0jT6SN0Ovvlpa3wX4rL5K1fTQuZCNKEB 4XPeUFYSQTJyVWdp3KBDblyWFg6nS71cmv1OmlNGCM/OOYHy8WMvuWarnxp+YhiL8x O3GLgNLQKeOTkLBqVPuKOplnoLt9woGjU5kW3skNkxkZg92xgCCf4TmKUGLoa7PCr4 JbUDKsLzipj6sk6IUeS38ZmvDFCc6Pnsk/n17M3FFqC/kA0fOY8RBpGI8OO3eKZQWY 9qIG/ZAeW45/si+wMrYkw4tIxKBdxLGoeVkl6ri9iNPnHaTVEfvOzpVJdLExKQtmo5 IgWOx/Pv31qig==
Subject: Re: [Insipid] Next version of the backwards compatibility proposal
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 15:36:59 -0000

James,

This draft is a little hard to follow because the examples all use 
Alice, Bob, Carol, but sometimes they are Kaplan implementations and 
sometimes they are Jones implementations. It would be easier to read if 
a name always corresponded to the same type of implementation. (E.g., 
Katy, Jan, Jerry.)

But since its transient, it may not be worth changing.

Otherwise, I think you make your point that other indicators aren't needed.

	Thanks,
	Paul

On 10/24/13 6:26 PM, James Polk wrote:
> INSIPID
>
> Here is the next version of the proposal for backwards compatibility
> between the insipid and kaplan versions of the Session-ID header.
>
> http://www.ietf.org/internet-drafts/draft-polk-insipid-bkwds-compatibility-proposal-03.txt
>
>
> There is a new section dealing with alternative proposals for a 'flag'
> to indicate which implementation an endpoint is, namely either a new
> option tag or a Contact header feature tag. I list the reasons why I
> don't think either will work.
>
> I'd like to get this draft discussed, as well as the two alternative
> flags on the list before we have our face2face in Vancouver on Monday
> evening, Nov 4th.
>
> James
>
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid
>