Subject: I-D Publication Request: draft-ietf-netconf-beep-05.txt

From: Andy Bierman <[email-masked]>
Date: Thu, 07 Jul 2005 19:20:46 -0700

[Area] OPS-NM
[WG]   NETCONF
[I-D]  draft-ietf-netconf-beep-05.txt
[Qver] draft-ietf-proto-wgchair-doc-shepherding-05.txt
[Shep] Andy Bierman <[email-masked]>

1.a) Yes, the WG Chairs have reviewed this version of the
     document, and believe it is ready for publication.

1.b) Yes the document has had adequate review.  Several
     WG members have reviewed this document.  It has also been
     reviewed by non-WG members very familiar with BEEP.

1.c) There are no open issues, and no further review is
     required, for this document.

1.d) There are no concerns with this document at this time.
     It is possible that clarifications will be identified
     as implementation and interoperability experience is
     reported to the WG.  

1.e) There is overwhelming WG consensus for this document.
     It is expected that more complex network applications
     (e.g., 1st or 3rd party commercial applications) will
     use this application mapping for NETCONF.

1.f) No appeals have been threatened against this document.

1.g) There are some minor ID-nits that will be fixed
     before RFC publication. (See ID-nit log below).

1.h) Yes, references are split.
     Yes, there is a reference to an unpublished document,
     namely the NETCONF Configuration Protocol document
     (draft-ietf-netconf-prot-07.txt), but this is also ready
     for publication.

1.j) I-D Submission Summary
    
Technical Summary

   This document specifies an application protocol mapping for the
   NETCONF protocol over the Blocks Extensible Exchange Protocol (BEEP).

Working Group Summary
 
   The NETCONF Working Group has consensus to publish this document
   as a Proposed Standard.  

Protocol Quality

   It is likely that there are several implementations of this
   document in various stages of completion at this time.
   Several major equipment vendors have indicated interest in
   supporting this document, and some non-commercial
   implementations are also expected.  The WG would like to
   thank Marshall Rose for his assistance with portions
   of this document.

----------------

[ID-nit log]

idnits 1.74

tmp/draft-ietf-netconf-beep-05.txt:

tmp/draft-ietf-netconf-beep-05.txt(5):
  Line is too long: the offending characters are '5'
tmp/draft-ietf-netconf-beep-05.txt(24):
   Line is too long: the offending characters are 's'
tmp/draft-ietf-netconf-beep-05.txt(44):
   Line is too long: the offending characters are '.'
tmp/draft-ietf-netconf-beep-05.txt(61):
   Line is too long: the offending characters are '3'
tmp/draft-ietf-netconf-beep-05.txt(62):
   Line is too long: the offending characters are '3'
tmp/draft-ietf-netconf-beep-05.txt(63):
   Line is too long: the offending characters are '4'
tmp/draft-ietf-netconf-beep-05.txt(64):
   Line is too long: the offending characters are '4'
tmp/draft-ietf-netconf-beep-05.txt(65):
   Line is too long: the offending characters are '4'
tmp/draft-ietf-netconf-beep-05.txt(66):
   Line is too long: the offending characters are '6'
tmp/draft-ietf-netconf-beep-05.txt(67):
   Line is too long: the offending characters are '6'
tmp/draft-ietf-netconf-beep-05.txt(68):
   Line is too long: the offending characters are '6'
tmp/draft-ietf-netconf-beep-05.txt(69):
   Line is too long: the offending characters are '8'
tmp/draft-ietf-netconf-beep-05.txt(70):
   Line is too long: the offending characters are '9'
tmp/draft-ietf-netconf-beep-05.txt(71):
   Line is too long: the offending characters are '0'
tmp/draft-ietf-netconf-beep-05.txt(72):
   Line is too long: the offending characters are '1'
tmp/draft-ietf-netconf-beep-05.txt(73):
   Line is too long: the offending characters are '1'
tmp/draft-ietf-netconf-beep-05.txt(74):
   Line is too long: the offending characters are '1'
tmp/draft-ietf-netconf-beep-05.txt(75):
   Line is too long: the offending characters are '2'
tmp/draft-ietf-netconf-beep-05.txt(76):
   Line is too long: the offending characters are '3'
tmp/draft-ietf-netconf-beep-05.txt(77):
   Line is too long: the offending characters are '4'
tmp/draft-ietf-netconf-beep-05.txt(119)
  : Line is too long: the offending characters are 'r'
tmp/draft-ietf-netconf-beep-05.txt(125)
  : Line is too long: the offending characters are 's'
tmp/draft-ietf-netconf-beep-05.txt(136)
  : Line is too long: the offending characters are 'e'
tmp/draft-ietf-netconf-beep-05.txt(182)
  : Line is too long: the offending characters are 't'
tmp/draft-ietf-netconf-beep-05.txt(277)
  : Line is too long: the offending characters are 's'
tmp/draft-ietf-netconf-beep-05.txt(294)
  : Line is too long: the offending characters are 'o'
tmp/draft-ietf-netconf-beep-05.txt(295)
  : Line is too long: the offending characters are 'P'
tmp/draft-ietf-netconf-beep-05.txt(297)
  : Line is too long: the offending characters are '.'
tmp/draft-ietf-netconf-beep-05.txt(299)
  : Line is too long: the offending characters are 'e'
tmp/draft-ietf-netconf-beep-05.txt(311)
  : Line is too long: the offending characters are 'd'
tmp/draft-ietf-netconf-beep-05.txt(312)
  : Line is too long: the offending characters are ','
tmp/draft-ietf-netconf-beep-05.txt(406)
  : Line is too long: the offending characters are ','
tmp/draft-ietf-netconf-beep-05.txt(408)
  : Line is too long: the offending characters are 'y'
tmp/draft-ietf-netconf-beep-05.txt(414)
  : Line is too long: the offending characters are 'r'
tmp/draft-ietf-netconf-beep-05.txt(415)
  : Line is too long: the offending characters are '.'
tmp/draft-ietf-netconf-beep-05.txt(422)
  : Line is too long: the offending characters are 't'
tmp/draft-ietf-netconf-beep-05.txt(441)
  : Line is too long: the offending characters are 'e'
tmp/draft-ietf-netconf-beep-05.txt(518)
  : Line is too long: the offending characters are 'b'
tmp/draft-ietf-netconf-beep-05.txt(608)
  : Line is too long: the offending characters are ','
tmp/draft-ietf-netconf-beep-05.txt(697)
  : Line is too long: the offending characters are 'd'
tmp/draft-ietf-netconf-beep-05.txt(770)
  : Line is too long: the offending characters are 'n'

  Checking nits according to http://www.ietf.org/ID-Checklist.html:
    Checking conformance with RFC 3978/3979 boilerplate...
    the boilerplate looks good.
    No nits found.

  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:
  - It seems as if not all pages are separated by form feeds - found 0
    form feeds but 14 pages

  Miscellaneous warnings:
    None.

    No nits found.

--
to unsubscribe send a message to [email-masked] with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>