Re: [Insipid] Timing for publishing draft-kaplan-insipid-session-id

<R.Jesske@telekom.de> Wed, 11 September 2013 11:04 UTC

Return-Path: <R.Jesske@telekom.de>
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 5854711E8221 for <insipid@ietfa.amsl.com>; Wed, 11 Sep 2013 04:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-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 oqOwFGtil6RC for <insipid@ietfa.amsl.com>; Wed, 11 Sep 2013 04:04:30 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) by ietfa.amsl.com (Postfix) with ESMTP id EF5AD11E821E for <insipid@ietf.org>; Wed, 11 Sep 2013 04:04:29 -0700 (PDT)
Received: from he113472.emea1.cds.t-internal.com ([10.134.93.130]) by tcmail11.telekom.de with ESMTP/TLS/AES128-SHA; 11 Sep 2013 13:04:26 +0200
Received: from HE113667.emea1.cds.t-internal.com ([fe80::c943:1394:e86e:fce3]) by HE113472.emea1.cds.t-internal.com ([::1]) with mapi; Wed, 11 Sep 2013 13:04:26 +0200
From: R.Jesske@telekom.de
To: atle.monrad@ericsson.com, gonzalo.camarillo@ericsson.com, insipid@ietf.org
Date: Wed, 11 Sep 2013 13:04:26 +0200
Thread-Topic: [Insipid] Timing for publishing draft-kaplan-insipid-session-id
Thread-Index: AQHOrkAj9fjUoLycQUyr/plInjtJEJm/KJcAgAE0VEA=
Message-ID: <058CE00BD4D6B94FAD033A2439EA1E4B01DD50B0F2B0@HE113667.emea1.cds.t-internal.com>
References: <522F442E.4040801@ericsson.com> <7D2F7D7ADBA812449F25F4A69922881C19B533@ESESSMB203.ericsson.se>
In-Reply-To: <7D2F7D7ADBA812449F25F4A69922881C19B533@ESESSMB203.ericsson.se>
Accept-Language: en-US, de-DE
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Wed, 11 Sep 2013 11:04:34 -0000

+1

BR
Roland

-----Ursprüngliche Nachricht-----
Von: insipid-bounces@ietf.org [mailto:insipid-bounces@ietf.org] Im Auftrag von Atle Monrad
Gesendet: Dienstag, 10. September 2013 18:39
An: Gonzalo Camarillo; insipid@ietf.org
Betreff: Re: [Insipid] Timing for publishing draft-kaplan-insipid-session-id

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