Re: [Mipshop] Gauging interest in official WG adoption of internet drafts

Lakshminath Dondeti <ldondeti@qualcomm.com> Sun, 26 March 2006 01:36 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNKBV-0005rr-DA; Sat, 25 Mar 2006 20:36:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FNKBU-0005rm-JG for mipshop@ietf.org; Sat, 25 Mar 2006 20:36:48 -0500
Received: from ithilien.qualcomm.com ([129.46.51.59]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FNKBU-0002Np-3H for mipshop@ietf.org; Sat, 25 Mar 2006 20:36:48 -0500
Received: from crowley.qualcomm.com (crowley.qualcomm.com [129.46.61.151]) by ithilien.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k2Q1akAF023154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 25 Mar 2006 17:36:47 -0800
Received: from LDONDETI.qualcomm.com (qconnect-10-50-69-1.qualcomm.com [10.50.69.1]) by crowley.qualcomm.com (8.13.5/8.12.5/1.0) with ESMTP id k2Q1ahGm001555 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 25 Mar 2006 17:36:45 -0800 (PST)
Message-Id: <6.2.5.6.2.20060325172313.04096678@qualcomm.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 25 Mar 2006 17:36:46 -0800
To: Yoshihiro Ohba <yohba@tari.toshiba.com>, gabriel montenegro <gabriel_montenegro_2000@yahoo.com>
From: Lakshminath Dondeti <ldondeti@qualcomm.com>
Subject: Re: [Mipshop] Gauging interest in official WG adoption of internet drafts
In-Reply-To: <20060326002555.GC17967@steelhead>
References: <20060322074936.65932.qmail@web81910.mail.mud.yahoo.com> <20060326002555.GC17967@steelhead>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Cc: mipshop@ietf.org
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mipshop.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
Errors-To: mipshop-bounces@ietf.org

Disclaimer: I work with one of the authors (Vidya) of the 
handover-keys-aaa I-D, although didn't contribute to the draft in anyway.

I just read the parts of the I-D that seem to be contentious and note 
that the reference to AMSKs is merely an example and the HMK can be 
established through other means, say by preprovisioning.

That said, I think it is best to remove Appendix A (I am not sure 
about A.1, that probably should stay and resolved later) as it 
reproduces a key hierarchy and key derivation process that is still 
under active discussion.

regards,
Lakshminath

At 04:25 PM 3/25/2006, Yoshihiro Ohba wrote:
>I have a reservation on draft-vidya-mipshop-handover-keys-aaa-01.txt.
>
>The draft describes a AAA-assisted key management protocol to generate
>handover keys for protecting signaling between MN and AR.  I am
>viewing the proposal as an application keying for FMIPv6 and possibly
>other protocols.  However, in the IETF65 hoakey BOF, Sam Hartman, a
>Security AD, raised concern on application keying.  As a consequence,
>the hoakey BOF chairs made a decision to exclude application keying
>from the BOF charter, expecting application keying to be discussed in
>a separate BOF.
>
>Thus, it might be wiser to hold this draft until there is a clear
>consensus on how to deal with application keying in the IETF.
>
>Best regards,
>Yoshihiro Ohba
>
>
>On Tue, Mar 21, 2006 at 11:49:36PM -0800, gabriel montenegro wrote:
> > Folks,
> >
> > In today's meeting we talked about 4 potential items up for 
> adoption as official working
> > groups. Talking with folks after the meeting, we've decided to 
> add two more to the list
> > of items we'll ask the WG whether we should adopt. This is the 
> follow-up email to today's
> > discussion, to make sure we ask this on the mailing list.
> >
> > So the question to the WG is: Should we adopt the following 
> documents as official WG
> > items (based on the individual drafts as noted below)?:
> >
> > 1. draft-ietf-mipshop-fmipv6-rev-XX.txt
> > based on draft-koodli-mipshop-rfc4068bis-00.txt
> >
> > 2. draft-ietf-mipshop-handover-keys-aaa-XX.txt
> > based on  draft-vidya-mipshop-handover-keys-aaa-01.txt
> >
> > 3. draft-ietf-mipshop-handover-key-send-XX.txt
> > based on draft-kempf-mobopts-handover-key-01.txt (currently expired)
> >
> > 4. draft-ietf-mipshop-fh80216e-XX.txt
> > based on draft-jang-mipshop-fh80216e-02.txt
> >
> > 5. draft-ietf-mipshop-3gfh-XX.txt
> > based on draft-yokota-mipshop-3gfh-02.txt
> >
> > 6. draft-ietf-mipshop-cga-cba-XX.txt
> > based on draft-arkko-mipshop-cga-cba-03.txt
> >
> > Please send comments one way or another through April 4, 2006.
> >
> > Thanks,
> >
> > chairs
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam?  Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
> > _______________________________________________
> > Mipshop mailing list
> > Mipshop@ietf.org
> > https://www1.ietf.org/mailman/listinfo/mipshop
> >
>
>_______________________________________________
>Mipshop mailing list
>Mipshop@ietf.org
>https://www1.ietf.org/mailman/listinfo/mipshop


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