[Netext] next steps for netext

jari.arkko at piuha.net (Jari Arkko) Tue, 07 April 2009 04:44 UTC

From: "jari.arkko at piuha.net"
Date: Tue, 07 Apr 2009 07:44:09 +0300
Subject: [Netext] next steps for netext
In-Reply-To: <148a01c9b72a$c307fd80$40106f0a@china.huawei.com>
References: <49D5BB60.4090407@piuha.net> <00d301c9b439$77787b90$40106f0a@china.huawei.com> <49DA3C0D.20103@piuha.net> <148a01c9b72a$c307fd80$40106f0a@china.huawei.com>
Message-ID: <49DADA19.8090200@piuha.net>

> 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