Re: [Last-Call] [MBONED] Genart last call review of draft-ietf-mboned-deprecate-interdomain-asm-05

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

 



From: Tim Chown <Tim.Chown@xxxxxxxxxx> 

"https://tools.ietf.org/html/draft-ietf-mboned-deprecate-interdomain-asm-05#section-4.5.  Preferring SSM applications intradomain

   If feasible, it is recommended for applications to use SSM even if
   they are initially only meant to be used in intradomain environments
   supporting ASM.  Because PIM-SSM is a subset of PIM-SM, existing
   intradomain PIM-SM networks are automatically compatible with SSM
   applications.  Thus, SSM applications can operate alongside existing
   ASM applications.  SSM's benefits of simplified address management
   and significantly reduced operational complexity apply equally to
   intradomain use.

   However, for some applications it may be prohibitively difficult to
   add support for source discovery, so intradomain ASM may still be
   appropriate."

> This wording was the result of comments received from those using ASM within their own networks.

Indeed.

Just to be clear about why some of us might be sensitive to the wording. RFCs get in the hands of many people involved with network development, including those in a purely management role. So, even if, in principle, intradomain, network designers can twist and stretch RFCs to suit their needs, as long as they break nothing, in practice, network designers are not always able to benefit from this unwritten rule. "It says right here that SSM is preferred," the manager will complain, not necessarily getting all the fallout.

Happy New Year mboned!

Bert

-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call



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

  Powered by Linux