Hi Mark, The draft talks about "destination of the policy" as in the tail-end node of the SR Policy. It does not talk about the destination IP address in the packet.
You can consider this as a "default policy" on similar lines as a default route. Please see the section below which will cover one of the use-cases for steering over such SR policies to the null endpoint. https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-06#section-8.8.1 Hope that clarifies. Thanks, Ketan -----Original Message----- From: spring <spring-boun...@ietf.org> On Behalf Of Mark Smith Sent: 16 December 2019 06:36 To: SPRING WG <spring@ietf.org> Cc: i-d-annou...@ietf.org Subject: Re: [spring] I-D Action: draft-ietf-spring-segment-routing-policy-06.txt "The endpoint indicates the destination of the policy. The endpoint is specified as an IPv4 or IPv6 address and is expected to be unique in the domain. In a specific case (refer to Section 8.8.1), the endpoint can be the null address (0.0.0.0 for IPv4, ::0 for IPv6)." Per Internet Standard 3 / RFC 1122, 0.0.0.0 is an illegal IPv4 destination address.* Per RFC 4291, ::0 is an illegal IPv6 destination address. Regards, Mark. *People doing tricky things with 0.0.0.0 has cost me and a past employer 2 weeks of needless troubleshooting, delaying a product/service launch. http://lists.ausnog.net/pipermail/ausnog/2017-July/039402.html On Mon, 16 Dec 2019 at 11:08, <internet-dra...@ietf.org> wrote: > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. > This draft is a work item of the Source Packet Routing in Networking WG of > the IETF. > > Title : Segment Routing Policy Architecture > Authors : Clarence Filsfils > Siva Sivabalan > Daniel Voyer > Alex Bogdanov > Paul Mattes > Filename : draft-ietf-spring-segment-routing-policy-06.txt > Pages : 35 > Date : 2019-12-15 > > Abstract: > Segment Routing (SR) allows a headend node to steer a packet flow > along any path. Intermediate per-flow states are eliminated thanks > to source routing. The headend node steers a flow into an SR Policy. > The header of a packet steered in an SR Policy is augmented with an > ordered list of segments associated with that SR Policy. This > document details the concepts of SR Policy and steering into an SR > Policy. > > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-spring-segment-routing-pol > icy/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-spring-segment-routing-policy-0 > 6 > https://datatracker.ietf.org/doc/html/draft-ietf-spring-segment-routin > g-policy-06 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-spring-segment-routing-po > licy-06 > > > Please note that it may take a couple of minutes from the time of > submission until the htmlized version and diff are available at > tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > spring mailing list > spring@ietf.org > https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
