IETF Logo Mail Archive

Re: [Mip6] draft-patil-mip6-whyauthdataoption to be published as WG I-D

Francis Dupont <Francis.Dupont@enst-bretagne.fr> Sat, 10 September 2005 09:32 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE1iW-0006aa-8W; Sat, 10 Sep 2005 05:32:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EE1iV-0006aJ-IJ for mip6@megatron.ietf.org; Sat, 10 Sep 2005 05:32:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA24787 for <mip6@ietf.org>; Sat, 10 Sep 2005 05:32:01 -0400 (EDT)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EE1m8-0002L3-O5 for mip6@ietf.org; Sat, 10 Sep 2005 05:35:57 -0400
Received: from givry.rennes.enst-bretagne.fr (givry.rennes.enst-bretagne.fr [193.52.74.194]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id j8A9Vj315732; Sat, 10 Sep 2005 11:31:45 +0200
Received: from givry.rennes.enst-bretagne.fr (localhost.rennes.enst-bretagne.fr [127.0.0.1]) by givry.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id j8A9VjVt015754; Sat, 10 Sep 2005 11:31:45 +0200 (CEST) (envelope-from dupont@givry.rennes.enst-bretagne.fr)
Message-Id: <200509100931.j8A9VjVt015754@givry.rennes.enst-bretagne.fr>
From: Francis Dupont <Francis.Dupont@enst-bretagne.fr>
To: Basavaraj.Patil@nokia.com
Subject: Re: [Mip6] draft-patil-mip6-whyauthdataoption to be published as WG I-D
In-reply-to: Your message of Fri, 09 Sep 2005 15:33:03 CDT. <456943D540CFC14A8D7138E64843F85301A2CFAD@daebe101.NOE.Nokia.com>
Date: Sat, 10 Sep 2005 11:31:45 +0200
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: mip6@ietf.org
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org

 In your previous mail you wrote:

   The justifications for the authentication option specified in WG I-D:
   "Authentication Protocol for Mobile IPv6",
   draft-ietf-mip6-auth-protocol are captured in the following I-D:
   "Why Authentication Data suboption is needed for MIP6",
   draft-patil-mip6-whyauthdataoption.
   
   In order to progress the WG I-D: draft-ietf-mip6-auth-protocol, we
   need to publish the whyauthdataoption ID as a WG document.

=> I don't understand the "as a WG document"? If there is delay
constraint to make it a WG document just add an extra delay.
Or do you suggest the RFC editor is faster for WG documents
(it should not)?

   The whyauthdataoption ID MAY be progressed as an Informational RFC if
   necessary. 
   
=> this seems necessary.

Regards

Francis.Dupont@enst-bretagne.fr

_______________________________________________
Mip6 mailing list
Mip6@ietf.org
https://www1.ietf.org/mailman/listinfo/mip6

v2.23.0 | Report a Bug | By Email