FYI... Comments and issues to me immediately, please. Tony
Begin forwarded message: > From: [email protected] > Date: February 7, 2011 9:56:10 AM PST > To: [email protected] > Cc: [email protected], [email protected], [email protected], > [email protected] > Subject: AUTH48 [AH]: RFC 6115 <draft-irtf-rrg-recommendation-16.txt> NOW > AVAILABLE > > > *****IMPORTANT***** > > Updated 2011/02/07 > > RFC Author(s): > -------------- > > Instructions for Completing AUTH48 in XML > > This is your last chance to make changes to your RFC-to-be: > draft-irtf-rrg-recommendation-16.txt. > Once the document is published as an RFC, we will not make changes. > Please follow the instructions below to complete the AUTH48 process. > > 1) Review the edited document completely. The files are available here: > > http://www.rfc-editor.org/authors/rfc6115.txt > http://www.rfc-editor.org/authors/rfc6115-diff.html > > We recommend reviewing the entire document, not just the diff file. > The placement of page breaks will be handled during the final stages of > publication (typically post-xml2rfc processing). > > 2) Review and resolve (as necessary) any questions raised by the RFC > Editor. The questions (if any) have been included in the XML file as > comments marked <!-- [rfced] ... --> and will be sent in a subsequent email. > > Retrieve the edited XML file here: > > http://www.rfc-editor.org/authors/rfc6115.xml > > (Note that you may need to view the page source to save the file.) > > 3) Send us your changes or respond with your approval for publication. > Please use 'Reply All' so that [email protected] and the parties > CC'ed on this message receive your response. Note that your document will > not move forward until we have received approvals from each of the > authors listed on the front page. > > If sending changes, please do one of the following: > > a. Update the provided XML file, then email us the revised XML file. > You may use any filename for the revised file; we will rename it > before posting it. > > --OR-- > > b. Provide us with an explicit list of changes in the this format. > > Section # (or indicate Global) > > OLD: > old text > > NEW: > new text > > Be sure to pay particular attention to these areas of the document: > - IANA Considerations updates (if applicable) > - Contact information > - Copyright notice and legends (see item 5 for more details) > > 4) Review changes submitted by your coauthors. We assume that you > will speak up if you do not agree with the proposed changes. That is, > your silence is your assent to changes submitted by your coauthors. > Note that any changes that are beyond editorial will be sent to the > relevant body for approval. > > Additional diff files will be posted as authors send updates for the > document. We recommend viewing these later diff files to identify and > review changes submitted by your coauthors. > > 5) Review the copyright notice and legends as defined in RFC 5378 and > the Trust Legal Provisions (TLP -- http://trustee.ietf.org/license-info/). > > If your document was approved for publication with a pre-RFC-5378 > copyright notice, we have applied the text from section 6.c.iii of the > TLP. Please consider whether this text is required (note that the > 6.c.iii text is not applicable to Independent Stream RFCs). See item > 4.5 of the "Copyright FAQ" at http://trustee.ietf.org/faqs.html for > guidance on whether this text applies to your document. > > 6) Please reply, as the document will not be published until we receive > approvals from each author. The details of the AUTH48 status of your > document are here: > > http://www.rfc-editor.org/auth48/rfc6115 > > Thank you for your cooperation, > > RFC Editor > > -------------------------------------- > RFC6115 (draft-irtf-rrg-recommendation-16) > -------------------------------------- > Title : Recommendation for a Routing Architecture > Author(s) : T. Li, Ed. > > _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
