AW: [Mobopts] RE: [Mipshop] AW: [Mobopts] Presentationslides for "CXTP using GIST"

["Tschofenig, Hannes" <[e-mail]>]

hi hui, 

during the meeting we ran out of time. 
maybe he phrased in such a way that one could interpret it in a wrong way. 

regarding <draft-housley-aaa-key-mgmt-01.txt>: key derivation and key transport in mobility scenarios is an area of ongoing investigation.

ciao
hannes


> -----Ursprüngliche Nachricht-----
> Von: [e-mail] 
> [mailto:[e-mail]] Im Auftrag von "DENG, HUI -HCHBJ"
> Gesendet: Mittwoch, 23. November 2005 07:07
> An: James Kempf; Tschofenig, Hannes; Xiaoming Fu; 
> [e-mail]; [e-mail]
> Cc: Xiaoming Fu
> Betreff: [Mobopts] RE: [Mipshop] AW: [Mobopts] 
> Presentationslides for "CXTP using GIST"
> 
> 
> As recalled during the mobopts session in Vancouver,
> Xiaoming said that one of their motivation is to solve this issue?
> 
> -Hui
> 
> > -----Original Message-----
> > From: James Kempf [mailto:[e-mail]] 
> > Sent: 2005年11月23日 1:04
> > To: Tschofenig, Hannes; DENG, HUI -HCHBJ; Xiaoming Fu; 
> > [e-mail]; [e-mail]
> > Cc: Xiaoming Fu
> > Subject: Re: [Mipshop] AW: [Mobopts] Presentation slides for 
> > "CXTP using GIST"
> > 
> > 
> > IPsec context is pretty much out, unless what is exchanged 
> > does not involve 
> > the shared key. So is any AAA context that involves a shared 
> > key. Please see 
> > http://www.ietf.org/internet-drafts/draft-housley-aaa-key-mgmt
> > -01.txt for a 
> > discussion of why propagating shared keys in this manner is 
> > not secure. The 
> > draft talks specifically about AAA-derived keys, but could 
> as well be 
> > applied to IPsec derived keys.
> > 
> >             jak
> > 
> > ----- Original Message ----- 
> > From: "Tschofenig, Hannes" <[e-mail]>
> > To: "DENG, HUI -HCHBJ" <[e-mail]>; "Xiaoming Fu" 
> > <[e-mail]>; <[e-mail]>; <[e-mail]>
> > Cc: "Xiaoming Fu" <[e-mail]>
> > Sent: Monday, November 21, 2005 5:23 AM
> > Subject: [Mipshop] AW: [Mobopts] Presentation slides for 
> > "CXTP using GIST"
> > 
> > 
> > > hi hui
> > >
> > > there are two issues to discuss:
> > >
> > > a) which security mechanisms you use for protection of the context
> > > transfer between the old ar and the new ar.
> > >
> > > b) which context you transfer between these devices.
> > >
> > > i could not remember xiaoming and john proposing to 
> > transfer ipsec sas 
> > > as
> > > part of (b). if you would like to transfer ipsec sas then 
> the past 
> > > investigations in, for example, 
> > <draft-hk-seamoby-ct-ipsec-00.txt> or 
> > > <draft-gopal-seamoby-ipsecctxt-issues-01.txt> might be 
> > worth taking a 
> > > look.
> > >
> > > ciao
> > > hannes
> > >
> > >> -----Ursprüngliche Nachricht-----
> > >> Von: [e-mail] 
> [mailto:[e-mail]] Im 
> > >> Auftrag von DENG, HUI -HCHBJ
> > >> Gesendet: Montag, 21. November 2005 14:05
> > >> An: Xiaoming Fu; [e-mail]; [e-mail]
> > >> Cc: John Loughney; Xiaoming Fu
> > >> Betreff: RE: [Mobopts] Presentation slides for "CXTP using GIST"
> > >>
> > >> Hi, Xiaoming
> > >>
> > >> I am still wondering how could you handle IPsec SA transfer, 
> > >> expecially initialize vector and anti-replay window.
> > >>
> > >> Thanks
> > >>
> > >> -Hui
> > >>
> > >>
> > >> -----Original Message-----
> > >> From: Xiaoming Fu [mailto:[e-mail]]
> > >> Sent: 2005-11-20 (星期日) 3:10
> > >> To: [e-mail]; [e-mail]
> > >> Cc: John Loughney; Xiaoming Fu
> > >> Subject: [Mobopts] Presentation slides for "CXTP using GIST"
> > >>
> > >>
> > >>
> > >> Hi all,
> > >>
> > >> Due to time limitation, mostly the Q&As in response to
> > >> some reviewers'
> > >> comments were discussed in the MOBOPTS RG meeting. For anyone 
> > >> interested in this draft, the slides are available in the 
> > following 
> > >> link:
> > >>
> > >> http://user.informatik.uni-goettingen.de/~fu/temp/cxtpgist/CXT
> > > PusingGIST_IETF64.ppt
> > >>
> > >> Please drop me/us a message if you think it may be
> > >> useful, or any
> > >> (additional) comments/suggestions you might have.
> > >>
> > >> Cheers,
> > >> Xiaoming
> > >>
> > >> _______________________________________________
> > >> Mobopts mailing list
> > >> [e-mail] https://www1.ietf.org/mailman/listinfo/mobopts
> > >>
> > >> +zy'í²‡+jwbÆ­!'ڟ&y'~'^ؚݙz-yÖ§Úºh,v!zz+vb隊V+-jGzí¡·Þ¶ʋ^{^ם"'^jǧ
> > >> ؟^ze隊V'jhțuץzע*.&^̬颚g^+az~׫!ޞm觵yr*bz{r鮲)b隊
> > Z+jZr+v+{^-^ֆ)^Zuz}+$yh
> > >> Þ·
> > >> +y޲'&+r~ڟ'(z0'!(!}y~b
> > >>
> > >
> > 
> > 
> > --------------------------------------------------------------
> ------------------
> > 
> > 
> > > _______________________________________________
> > > Mipshop mailing list
> > > [e-mail] https://www1.ietf.org/mailman/listinfo/mipshop
> > > 
> > 
> > 
> > 
> Disclaimer:
> The contents of this e-mail, and its attachments, if any, are 
> confidential and may be protected
> by law against any unauthorized use.  If you have received 
> this e-mail by mistake or have
> reason to believe that you are not the intended recipient, 
> please notify the sender by reply
> e-mail as soon as possible and delete it from your computer 
> system immediately thereafter.
> If you are not the intended recipient, you must not copy this 
> e-mail or attachment or disclose
> the contents to any other person.  While we have made every 
> effort to keep our network virus free,
> we take no responsibility for any computer virus which might 
> be transferred by way of this e-mail.
> 
> _______________________________________________
> Mobopts mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/mobopts
> 

_______________________________________________
Mobopts mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/mobopts