RFC 3941:Negative-Acknowledgment (NACK)-Oriented R...
RFC-Ref

address


Click on the red underlined text to get to the source

... multicast applications and users [3]. This document addresses the creation of negative-acknowledgment (NACK)- ...
... issues relevant to NORM protocol design, it specifically addresses in detail the following building blocks which are not addressed in other IETF documents ...


... protocol design goals and assumptions. These are areas that each protocol instantiation will need to address in detail. Each building block description in this document will include a discussion of the impact ...
... [9] have been created to address areas outside of the scope of this document. NORM protocol instantiations may depend upon these other ...
... NORM but may be used in concert with the other building block areas. In some cases, a building block may be able address a wide range of assumptions, while in other cases there will be trade-offs required to meet different application needs ...


... group. Identity based on arriving packet source addresses is insufficient for several reasons. These reasons include routing changes for hosts ...
... hosts with multiple interfaces that result in different packet source addresses for a given host over time, network address translation ...
... source addresses for a given host over time, network address translation (NAT) or firewall ...


... Authors' Addresses ...


... copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf- ipr@ietf.org. ...



Google
Web
RFC-Ref