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

James Polk <jmpolk@cisco.com> Fri, 25 October 2013 18:51 UTC

Return-Path: <jmpolk@cisco.com>
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 370EC11E81CB for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 11:51:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 S+xDaAi7ziCp for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 11:51:09 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 4EC8111E813A for <insipid@ietf.org>; Fri, 25 Oct 2013 11:51:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1830; q=dns/txt; s=iport; t=1382727069; x=1383936669; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=wexoyJ+XtHQyXnX0eyVHeW3w8Dtu5j2yJEKX+hhCM4E=; b=VLjVwxjdYkIvmYbfq6GtN4rKFGwqbn5yZWy7nFSfNEiTP8NGbraLXAAU 34/8GFWKbMlnDj7Q+ZDB9G/o8CgvaTDm8Ts0IYM7jUHtl/zJsPYaj5mKU N1q3RBlnRJqFh3HMSsBIx/fCiltlXs1HTzlSHxI94Wuw8LPgNzIjTKVHW Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag0FACe9alKtJXG+/2dsb2JhbABZDoJ5OL5SS4EiFnSCJQEBAQMBAQEBNQI0EAsHBA4KCRUQDwoOMAYBEgmHeAYNuVKPWoQsA4k/oFKCZ10e
X-IronPort-AV: E=Sophos;i="4.93,572,1378857600"; d="scan'208";a="276738321"
Received: from rcdn-core2-3.cisco.com ([173.37.113.190]) by rcdn-iport-7.cisco.com with ESMTP; 25 Oct 2013 18:51:08 +0000
Received: from jmpolk-WS.cisco.com (rcdn-vpn-client-10-89-1-86.cisco.com [10.89.1.86]) (authenticated bits=0) by rcdn-core2-3.cisco.com (8.14.5/8.14.5) with ESMTP id r9PIp84X023380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Oct 2013 18:51:08 GMT
Message-Id: <201310251851.r9PIp84X023380@rcdn-core2-3.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 25 Oct 2013 13:51:08 -0500
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, insipid@ietf.org
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <526A8FE7.3070203@alum.mit.edu>
References: <201310242226.r9OMQ2Pv004316@rcdn-core2-1.cisco.com> <526A8FE7.3070203@alum.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Authenticated-User: jmpolk
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 18:51:18 -0000

Thanks for reviewing and commenting Paul

At 10:36 AM 10/25/2013, Paul Kyzivat wrote:
>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.)

I thought about doing this (where one 'name', e.g., Alice) is always 
a certain version of implementation, but it didn't make it into this rev.


>But since its transient, it may not be worth changing.
>
>Otherwise, I think you make your point that other indicators aren't needed.

Thanks for understanding (and agreeing  ;-) )

James


>         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
>
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
>https://www.ietf.org/mailman/listinfo/insipid