Re: Fwd: New Version Notification for draft-perkins-dmm-4283mnids-00.txt

"Sri Gundavelli (sgundave)" <[email protected]>
Newsgroups gmane.ietf.nemo
Message-ID <D0673DC3.16B4C2%[email protected]>
Hi Hui,

May be this is for Charlie and also Vijay from the ancient history. But, let me try.

The work in MIF is more about defining network/PVD identity. In one sense its similar to the PLMN ID construct. Where as the MN-Id extensions draft is more about generating MN-Identity based on other protocol identifiers and other physical device identifiers. We already have IMSI-based identifier, which is the IMSI-NAI; We needed similar identifier based on MAC address for Wi-Fi, and also others identifiers based on some other sources. So, this is more about extending the base 4283 work with new types.


Regards
Sri




From: Hui Deng <[email protected]<mailto:[email protected]>>
Date: Friday, October 17, 2014 7:14 PM
To: Sri Gundavelli <[email protected]<mailto:[email protected]>>
Cc: "Charles E. Perkins" <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: Re: [DMM] Fwd: New Version Notification for draft-perkins-dmm-4283mnids-00.txt

how it is related to :
http://www.ietf.org/id/draft-ietf-mif-mpvd-id-00.txt

-Hui

2014-10-16 17:03 GMT+08:00 Sri Gundavelli (sgundave) <[email protected]<mailto:[email protected]>>:
Charlie – Are you asking the WG/chairs  for draft adoption ? The current version can be a good starting point and can be taken up as the –00 version of the WG draft. Off course, you still have plenty of comments on additional types values that the draft still needs to address :), but the current version can be adopted as a WG draft, IMO.


Sri





From: "Charles E. Perkins" <[email protected]<mailto:[email protected]>>
Organization: Blue Skies
Date: Tuesday, September 23, 2014 12:09 PM
To: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Subject: [DMM] Fwd: New Version Notification for draft-perkins-dmm-4283mnids-00.txt

Hello folks,

We have published a ...-00 version of the MNIDs draft.  This is mainly for
reference purposes.  A new version should be out within a week or so,
incorporating the suggestions and comments from people who responded
to the earlier suggestion to revisit this work.

Regards,
Charlie P.



-------- Original Message --------
Subject:        New Version Notification for draft-perkins-dmm-4283mnids-00.txt
Date:   Tue, 23 Sep 2014 10:43:12 -0700
From:   <[email protected]><mailto:[email protected]>
To:     Charles E. Perkins <[email protected]><mailto:[email protected]>, Vijay Devarapalli <[email protected]><mailto:[email protected]>, Charles E.Perkins <[email protected]><mailto:[email protected]>



A new version of I-D, draft-perkins-dmm-4283mnids-00.txt
has been successfully submitted by Charles E. Perkins and posted to the
IETF repository.

Name:           draft-perkins-dmm-4283mnids
Revision:       00
Title:          MN Identifier Types for RFC 4283 Mobile Node Identifier Option
Document date:  2014-09-23
Group:          Individual Submission
Pages:          4
URL:            http://www.ietf.org/internet-drafts/draft-perkins-dmm-4283mnids-00.txt
Status:         https://datatracker.ietf.org/doc/draft-perkins-dmm-4283mnids/
Htmlized:       http://tools.ietf.org/html/draft-perkins-dmm-4283mnids-00


Abstract:
   Additional Identifier Types are proposed for use with the Mobile Node
   Identifier Option for MIPv6 (RFC 4283).




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

The IETF Secretariat






_______________________________________________
dmm mailing list
[email protected]<mailto:[email protected]>
https://www.ietf.org/mailman/listinfo/dmm

_______________________________________________
dmm mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dmm
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.