[Last-Call] Opsdir last call review of draft-ietf-pim-mofrr-tilfa-05

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Reviewer: Jürgen Schönwälder
Review result: Has Nits

I have reviewed draft-ietf-pim-mofrr-tilfa-05.txt. I am not deep into
multicast routing and hence I look at the document from a general
operational perspective.

I found the document to be well written, the example topology to
outline the limitations of existing approaches is much appreciated.

How is this extension deployed? Can it be deployed incrementally or do
all multicast routers have to understand the RPF Vector Attributes in
the PIM Join packet to work properly? And are there any further
recommendations	about debugging	operational or deployment errors, are
there procedures to verify that the calculated alternative routes or
is this	no different than with other fast multicast reroute
mechanisms?

Editorial nits:

- The acronym SID is used well before it is introduced on page 8,
  please introduce the acronyms where they are first used.



-- 
last-call mailing list -- last-call@xxxxxxxx
To unsubscribe send an email to last-call-leave@xxxxxxxx




[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux