Re: MN-ID extension beyong NAI for PMIPv6 (was: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps)

[Alexandru Petrescu <[e-mail]>]

Vijay Devarapalli wrote:
[...]
> 4283bis - There is no draft on this yet, but a need to update
> 4283 was identified on the NETLMM mailing list and then 
> discussed later on the mext mailing list. The update is to
> mainly include other subtypes for MN identifier. For example,
> the MAC address would be the new subtype. Currently the 
> document only defines NAI.

I mainly agree with that need.  I'm not sure however on the interactions 
with netlmm and pmipv6.  The idea about 4283 potential extension (extend 
MN-ID option to include something else than a NAI) that was developped 
in the netlmm pmipv6 discussion made a lot of sense to me there.  But 
I'm not following anylonger where is the pmipv6 overall mechanism/vision 
impacting this.  Maybe 4283bissing discussion should be done there?  I 
don't know?

Alex

> Finally, what happened to 
> draft-mitsuya-monami6-flow-distribution-policy-04.txt. I 
> thought this was also going to be adopted as a MONAMI6 WG 
> document. I might have missed some emails.
> 
> Vijay
> 
>> -----Original Message-----
>> From: marcelo bagnulo braun [mailto:[e-mail]] 
>> Sent: Friday, November 23, 2007 6:10 AM
>> To: [e-mail]
>> Subject: [MEXT] MIP6/NEMO/MONAMI6 WG drafts - Next steps 
>>
>> Folks,
>>
>> We have been discussing with our AD the way forward w.r.t. WG 
>> drafts inherited from the previous WGs (MIP6, NEMO and MONAMI6).
>>
>> We have grouped drafts into five categories and decided about 
>> the actions to be taken for drafts of each category:
>>
>> ---------------------------------------------------------------------
>>
>> Cat. I: former WG drafts submitted to IESG already
>>
>> Action: Address possible IESG Comments/Discusses as they surface.
>>
>> I-Ds:	draft-ietf-mip6-bootstrapping-integrated-dhc-05
>> 	draft-ietf-mip6-cn-ipsec-06
>> 	draft-ietf-mip6-ha-switch-05
>> 	draft-ietf-mip6-hiopt-08
>> 	draft-ietf-mip6-whyauthdataoption-04
>> 	draft-ietf-mip6-experimental-messages-03
>> 	draft-ietf-mip6-vsm-03
>>
>> ----------------------------------------------------------------------
>>
>> Cat. II: former WG drafts corresponding to MEXT charter work items
>>
>> Action: - MEXT to adopt drafts as WG drafts
>>          - authors to submit new versions if/when needed as 
>> draft- ietf-mext-...
>>
>> I-Ds (MEXT work item):	draft-ietf-nemo-mib-03 work item (B.3)
>> 			draft-ietf-nemo-prefix-delegation-02 (B.3)
>> 			draft-ietf-monami6-mipv6-analysis-04 (A.3)
>> 			
>> draft-ietf-monami6-multihoming-motivation-scenario-02 (A.3)
>> 			draft-ietf-monami6-multiplecoa-04 (A.3)
>> 			draft-ietf-mip6-hareliability-03 (A.2)
>> 			draft-ietf-mip6-nemo-v4traversal-05 (A.1)
>> 			draft-ietf-mip6-radius-02 (A.6)
>>
>> ----------------------------------------------------------------------
>>
>> Cat. III: individual drafts corresponding to MEXT charter work items
>> 	  that were accepted as former WG drafts but never 
>> submitted as such.
>>
>> Action: - MEXT to adopt drafts as WG drafts as long as the 
>> authors follow the
>>            conditions requested by the respective WG at the 
>> moment of acceptancy
>>          - authors to submit new versions if/when needed as 
>> draft- ietf-mext-...
>>
>> I-Ds (MEXT work item):	draft-eddy-nemo-aero-reqs-01 (A.5)
>> 			draft-soliman-monami6-flow-binding-04 (A.3)
>>
>> ----------------------------------------------------------------------
>>
>> Cat. IV: individual drafts corresponding to MEXT charter work items
>> 	 that were *conditionally* accepted as former WG drafts.
>>
>> Action: - authors to update drafts so that they fullfills conditions.
>>
>> I-Ds (MEXT work item):	draft-baldessari-c2ccc-nemo-req-01 (A.5)
>>
>> ----------------------------------------------------------------------
>>
>> Cat. V: former WG drafts without corresponding MEXT charter work item
>>
>> Action: - MEXT to include this drafts as part of the rechartering
>>            discussion.
>>
>> I-Ds:	draft-ietf-mip6-rfc4285bis-01
>> 	draft-ietf-mip6-generic-notification-message-00
>>
>> --------------------------------------------------------------
>> ----------
>>
>> Comments?
>>
>> Cheers,
>>
>> --
>> Julien and Marcelo, MEXT chairs
>>
>>
>> _______________________________________________
>> MEXT mailing list
>> [e-mail]
>> https://www1.ietf.org/mailman/listinfo/mext
>>
> 
> _______________________________________________
> MEXT mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/mext
> 


______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

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