Thanks to Balaji and Acee for clarification. Regarding Acee clarification, I think it is other way. If the “p-bit is not to be set (clear)”, then NSSA LSA may be originated without FA. If the “p bit is to be set”, the NSSA LSA must not be originated when no forwarding address is available. As per section 2.3 in RFC 3101
For an NSSA with no such network the forwarding address field may only be filled with an address from one of the its active interfaces or 0.0.0.0. If the P-bit is set, the forwarding address must be non-zero; otherwise it may be 0.0.0.0. If an NSSA requires the P-bit be set and a non-zero forwarding address is unavailable, then the route's Type-7 LSA is not originated into this NSSA. Please confirm. Some OSPFV3 NSSA implementations of different vendors, supported Translation of Type-7 with “no FA” but “p bit is set”, are translating to Type-5 LSAs. If new implementation strict to do not translate then, it may cause inter-op issues with such implementations. So whether new implementations are also required to support those LSA translation to make compatible with older ones? Regards, Veerendranath From: Acee Lindem (acee) [mailto:[email protected]] Sent: 10 August 2016 01:24 To: Balaji Ganesh (balagane) <[email protected]>; Veerendranatha Reddy Vallem <[email protected]>; OSPF WG List <[email protected]> Subject: Re: [OSPF] [OSPFv3] regarding p bit set and FA for NSSA (Type-7) LSAs Hi Veera, Balaji, While I was contributor to this RFC ;^), I can see it could use some more normative language to cover these cases where no IPv6 forwarding address is available. I basically agree with Balaji, if the P-bit is to be set in the NSSA-LSA, the LSA MAY be originated w/o a forwarding address (in OSPFv3 forward address encoding is optional). If the P-bit is to be clear in the NSSA-LSA, the NSSA-LSA MUST NOT be originated when no forwarding address is available. Thanks, Acee From: OSPF <[email protected]<mailto:[email protected]>> on behalf of "Balaji Ganesh (balagane)" <[email protected]<mailto:[email protected]>> Date: Tuesday, August 9, 2016 at 10:10 AM To: Veerendranatha Reddy Vallem <[email protected]<mailto:[email protected]>>, OSPF WG List <[email protected]<mailto:[email protected]>> Subject: Re: [OSPF] [OSPFv3] regarding p bit set and FA for NSSA (Type-7) LSAs Hi Veera, Please see inline.. Regards, Balaji From: OSPF [mailto:[email protected]] On Behalf Of Veerendranatha Reddy Vallem Sent: 09 August 2016 18:04 To: OSPF WG List <[email protected]<mailto:[email protected]>> Subject: [OSPF] [OSPFv3] regarding p bit set and FA for NSSA (Type-7) LSAs Hi All, Can you please provide clarification for following in OSPFv3 NSSA implementation. As RFC 3101 is considered NSSA RFC for both OSPFv2 and OSPFv3, Case 1: As per RFC 3101, 2.4 section, While originating Type-7 LSA, if p –bit is set, then Forwarding address (FA) must be non- zero. [cid:[email protected]] For OSPFv3 case, there may be possible FA is not available (no global address is configured on any of NSSA interface). If OSPFv3 receives Type-7 LSA with p bit set but no forwarding address, whether this LSA should be consider as valid and can be used for route calculation? [BALAJI: If the Type-7 LSA has no forwarding address, it does not get translated to Type-5. This is specified in the RFC section 2.3, point 6 6. Those Type-7 LSAs that are to be translated into Type-5 LSAs must have their forwarding address set. However the LSA is still valid and would be used inside the NSSA area. ] Case 2: In section 3.2 , Translating Type-7 LSAs into Type-5 LSAs [cid:[email protected]] Same in OSPFv3, if we received Type-7 LSA with no forwarding address but ‘p’ bit set, whether ABR is allowed to translate this LSA to Type-5 External LSA? [BALAJI: No. ABR should not be translating such LSAs without forwarding address. This is again as per section 2.3, point 6 in the RFC.] As per my understanding, if Forwarding address is not available, Type-7 LSA must be originated with no ‘p’ bit set and no forwarding address. If ‘p’ bit is set means, it must always Carry forwarding address(for OSPFv3, it must be global ipv6 address configured on any of interfaces). [BALAJI: P-bit not being set would explicitly mean that we don’t want the LSA to be translated. Probably to keep the redistributed prefixes only within the NSSA area (for whatever reason it may be). If P-bit is set, it should also have a forwarding address for it to be translated.] Please let me know whether my understanding is correct or not for OSPFv3, as per RFC 3101. Regards, Veerendranath
_______________________________________________ OSPF mailing list [email protected] https://www.ietf.org/mailman/listinfo/ospf
