Re: [Insipid] Timing for publishing draft-kaplan-insipid-session-id
James Polk <jmpolk@cisco.com> Tue, 10 September 2013 23:10 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 2175211E8163 for <insipid@ietfa.amsl.com>; Tue, 10 Sep 2013 16:10:10 -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 qEzWTWH3-VVi for <insipid@ietfa.amsl.com>; Tue, 10 Sep 2013 16:09:55 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 756C611E81F7 for <insipid@ietf.org>; Tue, 10 Sep 2013 16:09:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2991; q=dns/txt; s=iport; t=1378854595; x=1380064195; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=4y2whZX+qPaJPeIH1ekB0eTlHFxiLMYXh28eiiB6LQo=; b=j21E+3tbqnWtdZl8FzR1HvdP9JNe17bcUL2e2imV7lorczM4lCg/k5W5 5xQ2BbI7HdhTjP7qidj294endIcaTpsOaZj/Z3CvCP8B/k4hvjSeWGk70 iynpgD0ECk8Nze5VFFa5Qu60H/NilzqMUDjWKcd3S13EZsyOlIAQcqmVJ I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhUFAOClL1KtJV2Y/2dsb2JhbABbAYMGOMMxgSMWdIIlAQEBBAEBATUCNBcEBwQRBAEBAQkVCQcPCg4fCQgGARIbh2cMwx2OEoFQBoQXA4k2j2+QPIM+HoE1
X-IronPort-AV: E=Sophos;i="4.90,881,1371081600"; d="scan'208";a="257875984"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP; 10 Sep 2013 23:09:54 +0000
Received: from jmpolk-WS.cisco.com ([10.89.10.22]) (authenticated bits=0) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r8AN9rbr007669 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 10 Sep 2013 23:09:53 GMT
Message-Id: <201309102309.r8AN9rbr007669@rcdn-core-1.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 10 Sep 2013 18:09:43 -0500
To: Atle Monrad <atle.monrad@ericsson.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>, "insipid@ietf.org" <insipid@ietf.org>
From: James Polk <jmpolk@cisco.com>
In-Reply-To: <7D2F7D7ADBA812449F25F4A69922881C19B533@ESESSMB203.ericsson .se>
References: <522F442E.4040801@ericsson.com> <7D2F7D7ADBA812449F25F4A69922881C19B533@ESESSMB203.ericsson.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Authenticated-User: jmpolk
Subject: Re: [Insipid] Timing for publishing draft-kaplan-insipid-session-id
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: Tue, 10 Sep 2013 23:10:10 -0000
Gonzalo I, however, do not agree with draft-kaplan-insipid-session-id being published as an informational RFC before the INSIPID solution is published as a standards-track. Nor do I want this document IANA registering the SIP header Session-ID, such as it currently attempts to do. At best, they should be consecutive RFC numbers with the INSIPID solution number having the lower number. If that means the kaplan draft has to wait in the RFC-Editor queue for the solution draft - so be it. That's what Dan R. from his Gen-Art review stated as his first major issue with the kaplan draft. Robert Sparks backed that opinion up by agreeing with that (and the rest of Dan's review). Gonzalo Salgueiro, one of INSIPID's WG chairs, says he stated that same view in a previously sent email to this list. INSIPID, from its inception, has had the charter item to IANA register this SIP header, and the draft-kaplan-insipid-session-id is not even a WG item, so why is everyone now in such a rush to have this draft do what a WG is supposed to do? Could it be the kaplan draft couldn't create a WG to form consensus on its own, so now folks are wanting to rush ahead of themselves to claim WG consensus where there wasn't any such consensus within any WG, let alone INSIPID? James At 11:39 AM 9/10/2013, Atle Monrad wrote: >Gonzalo > >I understood from the discussions in IETF that publishing of >draft-kaplan-insipid-session-id was to document what had been >already been documented in draft-kaplan-dispatch-session-id. > >If this still is the case, I do not see why waiting will help. > >I'd support publishing of draft-kaplan-insipid-session-id as soon >as possible. > >/atle > >________________________________ > > >Atle Monrad >3GPP CT Chairman > >Group Function Technology - Standardization and Technical Regulation >Ericsson > > > >-----Original Message----- >From: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] On >Behalf Of Gonzalo Camarillo >Sent: 10. september 2013 17:09 >To: insipid@ietf.org >Subject: [Insipid] Timing for publishing draft-kaplan-insipid-session-id > >Hi, > >as you know, the following draft has gone through an IETF LC and it >has gotten a few comments: > >http://datatracker.ietf.org/doc/draft-kaplan-insipid-session-id/ > >Some of the concerns relate to the fact that we are publishing this >document before INSIPID produces a solution document, which will be >backwards compatible with the solution described in the draft above. > >My question to this group is: do we have a reason to publish this >draft before the INSIPID solution draft is ready? > >Thanks, > >Gonzalo >_______________________________________________ >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
- Re: [Insipid] Timing for publishing draft-kaplan-… Andrew Allen
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- [Insipid] Timing for publishing draft-kaplan-insi… Gonzalo Camarillo
- Re: [Insipid] Timing for publishing draft-kaplan-… Atle Monrad
- Re: [Insipid] Timing for publishing draft-kaplan-… James Polk
- Re: [Insipid] Timing for publishing draft-kaplan-… Hadriel Kaplan
- Re: [Insipid] Timing for publishing draft-kaplan-… Atle Monrad
- Re: [Insipid] Timing for publishing draft-kaplan-… R.Jesske
- Re: [Insipid] Timing for publishing draft-kaplan-… DOLLY, MARTIN C
- Re: [Insipid] Timing for publishing draft-kaplan-… Laura Liess
- Re: [Insipid] Timing for publishing draft-kaplan-… James Polk
- Re: [Insipid] Timing for publishing draft-kaplan-… James Polk
- Re: [Insipid] Timing for publishing draft-kaplan-… Robert Sparks
- Re: [Insipid] Timing for publishing draft-kaplan-… Hadriel Kaplan
- Re: [Insipid] Timing for publishing draft-kaplan-… Charles Eckel (eckelcu)
- Re: [Insipid] Timing for publishing draft-kaplan-… Gonzalo Camarillo
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… Paul Kyzivat
- Re: [Insipid] Timing for publishing draft-kaplan-… Paul Kyzivat
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… Hadriel Kaplan
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… Paul E. Jones
- Re: [Insipid] Timing for publishing draft-kaplan-… Andrew Allen
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… DRAGE, Keith (Keith)
- Re: [Insipid] Timing for publishing draft-kaplan-… DRAGE, Keith (Keith)
- Re: [Insipid] Timing for publishing draft-kaplan-… Paul E. Jones
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Timing for publishing draft-kaplan-… Christer Holmberg
- Re: [Insipid] Fallback between legacy and WG solu… DRAGE, Keith (Keith)
- Re: [Insipid] Timing for publishing draft-kaplan-… James Polk
- Re: [Insipid] Fallback between legacy and WG solu… Christer Holmberg