IETF 94: Open Shortest Path First (OSPF) WG Agenda

Wednesday, November 4, 2015. 13:00 - 15:00 - Afternoon Session I

Location: Room 413
========================================================

Chairs: Acee Lindem
        Abhay Roy

WG Status Web Page: http://tools.ietf.org/wg/ospf/

1) Administrivia - 5 minutes
- Blue sheets
- Scribe/jabber
- Jabber room: ospf@jabber.ietf.org

2) WG Status Update - 10 minutes 
- Abhay Roy

See slides
Open question on S-BFD that needs answer from authors.

draft-ietf-ospf-mpls-elc-00 has expired.
Acee: Maybe not that important

3) OSPF WG Charter Update - 5 Minutes
- Acee Lindem

See slides
Charter is "self-perpetiuating".
Four(+1) tracks:
   Protocol extension using TLVs 
   Applications making use of TLVs
   Protocol Enhancements
   Security (Done - for now...)
   Manageability (YANG)

4) OSPFv3 Extended LSA Update - 10 Minutes 
- https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-lsa-extend/
- Acee Lindem

See slides
No comments/questions

5) OSPF SR Update - 15 Minutes 
- https://datatracker.ietf.org/doc/draft-ietf-ospf-segment-routing-extensions/
- https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv3-segment-routing-extensions/
- Acee Lindem for Peter Psenak

See slides
Alia: Please notify SPRING of last call
Acee: Conflict resolution separated so not fully necessary to notify
SPRING - but still useful to do so.

6) OSPF YANG Model - 15 Minutes 
- https://datatracker.ietf.org/doc/draft-ietf-ospf-yang/
- Derek Yeung  

See slides
Acee:Implementations support number and/or dotted form for OSPF area-id - 
but simpler in the model to use one form (dotted quad). 
Actual type used is not critical.

Acee: BFD config could be under BFD or under protocol - making container is a
way forward so that either approach can be supported.

Acee: Encourage folks to review policy model in RTGWG - see if you agree
with the  comments he has provided.

7)  OSPF Stub Neighbor - 10 Minutes
- https://datatracker.ietf.org/doc/draft-raza-ospf-stub-neighbor/
- Padma Pillay-Esnault

See slides
Note: Slides entitled: Scalable Hub and Spoke Topologies

Acee: Other hubs receive LSAs from other hubs so can detect misconfig
How does it know?
Padma: Check for default route

Philip Matthews: Can spokes be rings?
Padma : Yes
Acee: Works as long as it is isolated

Keyur: What if spoke wants a more specific route
Padma: Use poloicy

Alia: Can you handle spoke-spoke links?
Padma: Yes
Acee: Have to treat that as a single site because spokes become  multi-homed
Alia: Cannot dynamically create/destroy the spoke-spoke links then.
Alia: draft-hegde-rtgwg-virtual-multi-instance-00 presented in RTGWG - 
seems like solving the same problem. Please look at it.

Acee: Should we solve this problem in OSPF WG?
(Good support in the room)

Acee: May be IPR for this technology - multiple companies may have similar 
solutions

8) OSPF TE Values for non-TE Applications Alternatives - 10 Minutes
- https://datatracker.ietf.org/doc/draft-ppsenak-ospf-te-link-attr-reuse/
- Jeff Tantsura

See slides

Chris: Think discussion on mailing list is not yet resolved.

Les: Same problem exists in IS-IS - no work going on there. Should we
mandate that both potocols solve the problem in the same way?

Chris:What is a TE application? Is it RSVP?
Backwards compatibility issues. response seems to be should not have done this.
But this should be taken more seriously.
Jeff: If you use TED for non-TE you can still do that

Julien: Don't see the need for this - if we need SRLG then enable TE
Maybe more strict interprtation in OSPF
Jeff: Can still continue to enable TE as before
Julien: Don't see why it is cleaner.

Alia: Why is this a problem?
LFA needs SRLG info and this is only defined in TE
Share concerns about migration issues - need to solve operational issues.
Jeff: Can continue to use TED - info is still there
Alia: But when flood new way - partial deployment leads to interoperablility 
issues.
Is there operational pain enabling TE?

Julien: Is it enabling TE partially?
Jeff: No - moving info out of TE

Acee: Prefix link attributes will have much of this info - so this helps 
consolidate te informatiuon when not being used for TE.

Chris: New stuff OK - but leave existing TE info where it is
Acee: No - the info is used for two different purpose
Chris: Using SRLG as an example - mean the info may need to be advertised
 in both places
Acee: Depends on how you use it

Chris: Still need to know what TE application is

Acee: This issue needs more discussion

9) OSPF Prefix/Link Attribute Tags - 10 Minutes
- https://www.ietf.org/id/draft-acee-ospf-admin-tags-03.txt
- Acee Lindem

See slides

Acee: For NSSA and EXT LSAs must use the existing tag for the first tag