Document: draft-ietf-l3vpn-ospf-2547-02.txt
Review: Lucy E. Lynch
Date: 2 december 2004 

OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP VPNs
draft-ietf-l3vpn-ospf-2547-02.txt

"This draft is basically ready for publication, but has nits that should
be fixed before publication."

Just a comment here, I find it mildly disconcerting that this document
has seen no real changes from v.00 -> v.01 -> v.02 and very little
comment on the l3vpn mailing list. Is this just an exercise in covering
all the bases, or is there really a need for OSPF support at the CE?
The use of the term "sham link" is also a bit odd, although accurate.
If "Sham links SHOULD be treated by OSPF as OSPF Demand Circuits" maybe
they are really VODCs?

ID tracker already reflects most of the nits and the IANA related issues -
-------------------------------------------------------------------------
idnits 1.51

draft-ietf-l3vpn-ospf-2547-02.txt:

  Checking nits according to http://www.ietf.org/ID-Checklist.html:

    Checking conformance with RFC 3667/3668 boilerplate...
    the boilerplate looks good.
    There are 6 instances of too long lines in the document,

    -- the longest one being 3 characters in excess of 72.

    There are 674 instances of lines with non-ascii characters in the
document.


  Checking nits according to http://www.ietf.org/ietf/1id-guidelines.txt:

    The document seems to lack a 1id_guidelines paragraph about the list
    of current Internet-Drafts -- however, there's a paragraph with a
    matching beginning. Boilerplate error?


  Miscellaneous warnings:

    There are 8 instances of lines with hyphenated line breaks in the
    document.
    Line 789 has weird spacing: '...also be  possi...'

    Run idnits with the --verbose option for more detailed information.