Sorry, I didn't get your text in time to incorporate. I did craft a fragment regarding IANA myself, since I didn't get the IANA fragment in time. My fragment, in the section on "Request for Publication", reads:
> If the document requires any IANA allocations, authors should take > care to check the assignment policy for the relevant name space, > since some assignment policies (e.g., "IETF Consensus") cannot be > used by Independent Submissions. See RFC 2434 [RFC2434] for more > information. Danny McPherson sent a few editorial comments after my submission as well. I will incorporate both sets of feedback in an update once the submission window opens again. Thanks, -Dave > -----Original Message----- > From: Jari Arkko [mailto:[EMAIL PROTECTED] > Sent: Monday, March 05, 2007 1:17 AM > To: Dave Thaler > Cc: [email protected]; IAB > Subject: Re: [INDEP] Preview of draft-iab-rfc-independent-00.txt > > Dave Thaler kirjoitti: > > Attached is the current pre-submission version of the document. > > > > > After a quick look, it looks pretty good. > > > 1) Issue "4. Independent publication of documents resulting from IETF > > process" from Olaf's summary. > > > > Olaf proposed no change unless text was contributed. Jari had > > volunteered to submit some text for this (IANA issues, etc.) which I am > > still waiting for. > > > Sorry. But as Olaf mentioned, I posted a suggestion a short while ago, > hopefully you are still awake and able to deal with that... there were > two specific text fragments, one for syncing the treatment of was-in- > the-IETF-process submissions with this and iesg-sponsoring-guidelines, > and another one to note that independent submissions are under > the usual IANA rules. > > Jari > > _______________________________________________ INDEPENDENT mailing list [email protected] https://www1.ietf.org/mailman/listinfo/independent
