[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MEXT] EXTENDED [WGLC] RFC 3775 bis / draft-ietf-mext-rfc3775bis
- To: "Basavaraj.Patil at nokia.com" <Basavaraj.Patil at nokia.com>, "charles.perkins at earthlink.net" <charles.perkins at earthlink.net>, "arno at natisbad.org" <arno at natisbad.org>
- Subject: Re: [MEXT] EXTENDED [WGLC] RFC 3775 bis / draft-ietf-mext-rfc3775bis
- From: "Laganier, Julien" <julienl at qualcomm.com>
- Date: Fri, 9 Oct 2009 15:56:53 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Cc: "mext at ietf.org" <mext at ietf.org>
- Delivered-to: mext at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=julienl at qualcomm.com; q=dns/txt; s=qcdkim; t=1255129029; x=1286665029; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:references:in-reply-to:accept-language: content-language:x-ms-has-attach:x-ms-tnef-correlator: acceptlanguage:content-type:content-transfer-encoding: mime-version:x-ironport-av; z=From:=20"Laganier,=20Julien"=20<julienl at qualcomm.com> |To:=20"Basavaraj.Patil at nokia.com"=20<Basavaraj.Patil at nok ia.com>,=0D=0A=20=20=20=20=20=20=20=20"charles.perkins at ea rthlink.net"=20<charles.perkins at earthlink.net>,=0D=0A=20 =20=20=20=20=20=20=20"arno at natisbad.org"=20<arno at natisbad .org>|CC:=20"mext at ietf.org"=20<mext at ietf.org>|Date:=20Fri ,=209=20Oct=202009=2015:56:53=20-0700|Subject:=20RE:=20[M EXT]=20EXTENDED=20[WGLC]=20RFC=203775=20bis=20/=20draft-i etf-mext-rfc3775bis|Thread-Topic:=20[MEXT]=20EXTENDED=20[ WGLC]=20RFC=203775=20bis=20/=0D=0A=20draft-ietf-mext-rfc3 775bis|Thread-Index:=20AcpJJXQbKOxA6rTCTpKSlHVOoX6CMAAAaL FhAALZUwA=3D|Message-ID:=20<BF345F63074F8040B58C00A186FCA 57F1C2655D4F8 at NALASEXMB04.na.qualcomm.com>|References:=20 <4ACFA799.3080403 at earthlink.net>=0D=0A=20<C6F51495.2ECF2% basavaraj.patil at nokia.com>|In-Reply-To:=20<C6F51495.2ECF2 %basavaraj.patil at nokia.com>|Accept-Language:=20en-US |Content-Language:=20en-US|X-MS-Has-Attach: |X-MS-TNEF-Correlator:|acceptlanguage:=20en-US |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |Content-Transfer-Encoding:=20quoted-printable |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 300,2777,5766"=3B=20a=3D"24925184"; bh=YEFFCXpsQ8LXH0NfZf+0EPgzfS/hy9eEFWdCLz/0gL8=; b=C5RDlhciUkiUYJmUKki81ziBdLdbZSe52QFg3jdGPhJHFyHHYpM12/3w s7NBBoCEDbe4s22Az+P1ingxACZG+mqL/ggAG2ZfrnVXH+5X3kPxVlJyF QJK6wKlgZIM6jGwL/L2RZoHD7E3cwcqxGPup0HaiK9lbX9+DWXF3C2APq w=;
- In-reply-to: <C6F51495.2ECF2%basavaraj.patil at nokia.com>
- List-archive: <http://www.ietf.org/mail-archive/web/mext>
- List-help: <mailto:mext-request@ietf.org?subject=help>
- List-id: Mobile IPv6 EXTensions WG <mext.ietf.org>
- List-post: <mailto:mext@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
- References: <4ACFA799.3080403 at earthlink.net> <C6F51495.2ECF2%basavaraj.patil at nokia.com>
- Thread-index: AcpJJXQbKOxA6rTCTpKSlHVOoX6CMAAAaLFhAALZUwA=
- Thread-topic: [MEXT] EXTENDED [WGLC] RFC 3775 bis / draft-ietf-mext-rfc3775bis
Basavaraj,
Basavaraj Patil wrote:
>
> A few comments about some of the citations being proposed:
>
>
> On 10/9/09 4:14 PM, "Charles Perkins" <charles.perkins at earthlink.net>
> wrote:
>
> >> Considering the mechanism is implemented and such an interface
> needed to
> >> support that, 3775bis could at least point MIGRATE doc given below
> as an
> >> informational reference document. This clarifies the need and gives
> a
> >> possible solution.
> >>
> >> http://tools.ietf.org/html/draft-ebalard-mext-pfkey-enhanced-
> migrate-00
> >>
> >
> > So that I can finish revising rfc3775bis before having to stop and
> read
> > that draft,
> > can you provide some suggested text for the proposed citation? I'll
> try
> > to read the
> > draft in the next few days understand your citation and text.
>
> This reference does not add any value to 3775bis. It is more relevant
> in the
> context of 3776 or 4877. Adding this reference even in the Informative
> section is not required.
Speaking as an individual regarding whether or not addition of the reference is required: Well, informative references are by definition informative and are not required to be read to implement the specification. IMHO the reference does provide useful information since it points to an API between IPsec and MIPv6 which is implicitly assumed in the design of 3775.
That being said, I agree with you that such a reference would also be relevant in the context of 3776 and 4877.
--julien