OSPF WG Minutes - Wednesday March 25th, 2009
              Scribe: Russ White (russ@cisco.com), 
                      Edited by Acee Lindem (acee@redback.com)

Document Status - Acee Lindem - See Slides
    Notable Comments:
         OSPFv3 MIB in last stages. Will have short WG last call on a diff
           MIB doctor update. 
         OSPF TE Node Address will be WG last called shortly after IETF.
         HMAC-SHA1 under discussion.

     Dave Ward - Please address my comments on both the dynamic hostname
                 and multiple address family drafts. 
     Acee - Will do - we need to be careful as not to overly restrict the 
           instance ID space since it is very small (8 bits). 
         
OSPF Extensions in support of WSON - Greg Bernstein - See Slides 
    Notable Comments:
     Greg Bernstein - These extensions are used for provisioning
                      optical networks - not IP networks. 
     Dimitri Papadimitriou - There could be a problem with nodes with
                      interfaces in multiple areas.
     Greg - May need new top-level TLVs. The optical connectivity 
            matrix will change more frequently than the rest of the 
            information.
     Dimitri Papadimitriou - Need to determine correct TE LSAs for new
       TLVs. 
     Acee - Suggest everybody review.  
     Jonathan Sadler - There seems to be potential applicability to
                       things outside wavelength switched environments, or
                       a way of adding TE and other options on older equipment, 
                       etc, in the realm of TE.
      Acee - This is a problem for CCAMP. 
      Dimitri Papadimitriou: Need to determine correct TE LSAs for new
       TLVs. 
      Dimitri or Jonathan - Will the TLVs for optical exceed 64K bytes? 
      Greg: Doesn't expect this to happen in the next 20 years.  
 
LDP-IGP Sync on Broadcast Networks - Sri Kini - See Slides
       - MPLS Draft 
       _ Compatible with RFC 5443
      Notable Comments:
       Question: How is a cut-edge determined? 
       Sri Kini - During SPF, it is a cut-edge path if it is the only path 
                  to the broadcast network.
       Acee - What happens if not all routers on broadcast network support 
              this draft?    
       Sri - It is fully compatiable. Only routers supporting the draft
             will delay advertisement until LDP sync is complete. 
       Question: Why should this be standardized? 
       Acee: Even though the bits on the wire don't change, this is a
             protocol change since the behavior changes. 

OSPF Sparse Topologies - Acee Lindem - See Slides
      Notable Comments:
       Jonathan - Please restrict the transport information to non-routing
                  information. It could be non-IP routing information such
                  as GMPLS, optical, etc. 

OSPF Charter - Abhay Roy - See Slides 
       Abhay - Summary: Although we are late on some items, we are
               progressing many of the long standing documents. 
               We will accept new work but there must be a requirement
               and commitment to work on it. 
      Notable Comments on HMAC-SHAx: 
       Tony Li: Use of Apad in HMAC-SHAx doesn't make the algorithm stronger.
                It satisfies the primary customers consistency requirement 
                with neglible overhead. 
       Ran Atkinson: The DoD really does want Apad to be included in the
                     HMAC-SHAx computation.