[Netext] next steps for netext

Xiangsong.Cui at huawei.com (Xiangsong Cui) Tue, 07 April 2009 05:02 UTC

From: "Xiangsong.Cui at huawei.com"
Date: Tue, 07 Apr 2009 13:02:01 +0800
Subject: [Netext] next steps for netext
References: <49D5BB60.4090407@piuha.net> <00d301c9b439$77787b90$40106f0a@china.huawei.com> <49DA3C0D.20103@piuha.net> <148a01c9b72a$c307fd80$40106f0a@china.huawei.com> <49DADA19.8090200@piuha.net>
Message-ID: <14c501c9b73d$fcb6db60$40106f0a@china.huawei.com>

OK, I see.
Thanks a lot.

Xiangsong


????????  


??????????????? ???518129
http://www.huawei.com
-------------------------------------------------------------------------------------------------------------------------------------
????????????????????????????????????????
????????????????????????????????????????
???????????????????????????????????
This e-mail and its attachments contain confidential information from HUAWEI, which 
is intended only for the person or entity whose address is listed above. Any use of the 
information contained herein in any way (including, but not limited to, total or partial 
disclosure, reproduction, or dissemination) by persons other than the intended 
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by 
phone or email immediately and delete it!

  ----- Original Message ----- 
  From: Jari Arkko 
  To: Xiangsong Cui 
  Cc: netext at mail.mobileip.jp 
  Sent: Tuesday, April 07, 2009 12:44 PM
  Subject: Re: [Netext] next steps for netext



  > Do you mean that the "IETF scope" covers RFCs and WG drafts,
  > but not covers individual draft which has not been submitted
  > to IETF?
  >  

  Yes. There are some Internet Drafts that just exist as drafts and are 
  not being submitted by their authors for consideration as a WG document, 
  AD sponsored document, etc. Documents in or proposed to be included to 
  WGs, AD sponsosoring, and so on are within the current IETF scope.

  In the particular case of PMIP4, the authors have not asked IETF to 
  progress their specification. At the time that the draft was brought up, 
  it had already been implemented, and it was unlikely that there'd be any 
  changes, even if based on IETF review some might have been needed. So 
  after some discussion the authors simply requested the RFC Editor to 
  publish their document on the so called "Independent Submission" RFC 
  series. Its basically documenting vendors' and individuals' 
  specifications as-is.

  Jari
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mobileip.jp/pipermail/netext/attachments/20090407/baee7082/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: outlook_huawei_logo_cn.jpg
Type: image/jpeg
Size: 6737 bytes
Desc: not available
URL: <http://www.mobileip.jp/pipermail/netext/attachments/20090407/baee7082/attachment-0001.jpg>