RE: [netlmm] Issue: Auth Option support

"Alper Yegin" <alper.yegin@yegin.org> Tue, 07 August 2007 08:41 UTC

Return-path: <netlmm-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIKd0-0001Qj-OF; Tue, 07 Aug 2007 04:41:22 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IIKcz-0001Qe-MN for netlmm@ietf.org; Tue, 07 Aug 2007 04:41:22 -0400
Received: from mout.perfora.net ([74.208.4.194]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IIKcy-0008I4-AW for netlmm@ietf.org; Tue, 07 Aug 2007 04:41:21 -0400
Received: from [88.233.199.213] (helo=IBM52A5038A94F) by mrelay.perfora.net (node=mrus0) with ESMTP (Nemesis), id 0MKp8S-1IIKcu1WNe-0005rE; Tue, 07 Aug 2007 04:41:19 -0400
From: Alper Yegin <alper.yegin@yegin.org>
To: 'Sri Gundavelli' <sgundave@cisco.com>, netlmm@ietf.org
Subject: RE: [netlmm] Issue: Auth Option support
Date: Tue, 07 Aug 2007 11:41:13 +0300
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
In-reply-to: <Pine.GSO.4.63.0708070000100.13701@irp-view13.cisco.com>
Thread-Index: AcfYwQ6voKS1c0EASayvJIq8ADkrlQADOAAg
Message-ID: <0MKp8S-1IIKcu1WNe-0005rE@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX18LXUCVNC/8YepefruTJ49VZOVdnab+1trz46/ KUcftzWI5davfxPhB+5vbHi0yLc0SZ+slO4ARWo5Cn4iq6EtuU gU8lGCE5oqJ/6whAPt21Q==
X-Spam-Score: -0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc:
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
Errors-To: netlmm-bounces@ietf.org

> The issue was related to the use of MUST clause in specifying
> the IPSec requirement for Proxy Mobile IPv6 protocol. Alper
> was suggesting that we relax that requirement and potentially
> leave a room for Auth Option support in future.

Actually, I didn't mean it specifically for Auth Option. It can be anything.
Given that the security is handled by a separate protocol, why lock it down
to "IPsec", when some other protocol (Auth Option being one example) cannot
be used.

> But, as most people agreed and as supported by Jari, this can

My understanding was the opposite, especially about Jari's statement.

> always be changed in future when the support for new security
> mechanisms such as Auth Option are defined for Proxy Mobile IPv6
> and that specific document can always modify this requirement.
> So, no changes will be made to the document on this issue.

What if Auth Option is good enough as written?
What if a document in another SDO defines the alternative security
mechanism?

For the type of interop we are seeking in IETF, "MUST implement" is good
enough. "MUST use" is not necessary.

Alper





> 
> 
> Regards
> Sri
> 
> _______________________________________________
> netlmm mailing list
> netlmm@ietf.org
> https://www1.ietf.org/mailman/listinfo/netlmm


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