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

James Polk <jmpolk@cisco.com> Fri, 25 October 2013 19:47 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 02F8121F9FC6 for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 12:47:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.537
X-Spam-Level:
X-Spam-Status: No, score=-110.537 tagged_above=-999 required=5 tests=[AWL=0.062, 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 Brxt8Mb8scQN for <insipid@ietfa.amsl.com>; Fri, 25 Oct 2013 12:47:24 -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 D26EC11E8178 for <insipid@ietf.org>; Fri, 25 Oct 2013 12:47:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2987; q=dns/txt; s=iport; t=1382730444; x=1383940044; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=v6Mv+yIvNz6WvAfyR968rgftDbWNN6tNZ9lww5K9jSQ=; b=Ha+uNnpPM2aiCyt3aeT10Cp4lpE7kV/t6Tf1xc+5tvWTUvVZ+LIfS3+9 6hKwj/BinjpBfFpy3xnefBw4NO5/i2ZjMJ+41tCeuMaf4A8g50HBRwloq VTqU7WUMT1dYwMvi0Rl8qpC7GCIHPRx3xCcSMCetsh5WgWSdOCXEvtYkP o=;
X-IronPort-AV: E=Sophos;i="4.93,572,1378857600"; d="scan'208";a="276763450"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by rcdn-iport-7.cisco.com with ESMTP; 25 Oct 2013 19:47:23 +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-2.cisco.com (8.14.5/8.14.5) with ESMTP id r9PJlMXA028171 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Oct 2013 19:47:22 GMT
Message-Id: <201310251947.r9PJlMXA028171@rcdn-core2-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 25 Oct 2013 14:47:22 -0500
To: Christer Holmberg <christer.holmberg@ericsson.com>, James Polk <jmpolk@cisco.com>, Paul Kyzivat <pkyzivat@alum.mit.edu>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1C4F7111@ESESSMB209.ericss on.se>
References: <201310242226.r9OMQ2Pv004316@rcdn-core2-1.cisco.com> <526A8FE7.3070203@alum.mit.edu> <201310251851.r9PIp84X023380@rcdn-core2-3.cisco.com> <7594FB04B1934943A5C02806D1A2204B1C4F7111@ESESSMB209.ericsson.se>
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 19:47:29 -0000

That's an interesting suggestion. If others think this solves any 
confusion, and doesn't create more - I can use this in my slide deck in YVR...

-j

At 01:58 PM 10/25/2013, Christer Holmberg wrote:

>Alice could have different family names, depending on what type of 
>entity she represents: Alice Kaplan and Alice Jones :)
>
>
>
>Regards,
>
>
>
>Christer
>
>
>
>
>
>
>
>----------
>From: insipid-bounces@ietf.org [insipid-bounces@ietf.org] on behalf 
>of James Polk [jmpolk@cisco.com]
>Sent: Friday, 25 October 2013 9:51 PM
>To: Paul Kyzivat; insipid@ietf.org
>Subject: Re: [Insipid] Next version of the backwards compatibility proposal
>
>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-comp 
> atibility-proposal-03.txt>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>https://www.ietf.or 
> g/mailman/listinfo/insipid
> >
> >_______________________________________________
> >insipid mailing list
> >insipid@ietf.org
> ><https://www.ietf.org/mailman/listinfo/insipid>https://www.ietf.org 
> /mailman/listinfo/insipid
>
>_______________________________________________
>insipid mailing list
>insipid@ietf.org
><https://www.ietf.org/mailman/listinfo/insipid>https://www.ietf.org/mailman/listinfo/insipid