> On Mar 15, 2016, at 10:26 AM, Ted Lemon <[email protected]> wrote: > > When was the last document published that updated one of the IPv4 > specifications? > > Are we counting routing drafts?
By "one of the IPv4 specifications" do you mean RFC 791, or "a specification using IPv4"? If you mean "updates 791", That was February 2013: https://tools.ietf.org/html/rfc0791 0791 Internet Protocol. J. Postel. September 1981. (Format: TXT=97779 bytes) (Obsoletes RFC0760) (Updated by RFC1349, RFC2474, RFC6864) (Also STD0005) (Status: INTERNET STANDARD) (DOI: 10.17487/RFC0791) https://tools.ietf.org/html/rfc6864 6864 Updated Specification of the IPv4 ID Field. J. Touch. February 2013. (Format: TXT=44418 bytes) (Updates RFC0791, RFC1122, RFC2003) (Status: PROPOSED STANDARD) (DOI: 10.17487/RFC6864) If you mean "a specification using IPv4", that would have been in January 2016: https://tools.ietf.org/html/rfc6826 6826 Multipoint LDP In-Band Signaling for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths. IJ. Wijnands, Ed., T. Eckert, N. Leymann, M. Napierala. January 2013. (Format: TXT=23927 bytes) (Updated by RFC7438) (Status: PROPOSED STANDARD) (DOI: 10.17487/RFC6826) https://tools.ietf.org/html/rfc7246 7246 Multipoint Label Distribution Protocol In-Band Signaling in a Virtual Routing and Forwarding (VRF) Table Context. IJ. Wijnands, Ed., P. Hitchen, N. Leymann, W. Henderickx, A. Gulko, J. Tantsura. June 2014. (Format: TXT=24698 bytes) (Updated by RFC7438) (Status: PROPOSED STANDARD) (DOI: 10.17487/RFC7246) https://tools.ietf.org/html/rfc7438 7438 Multipoint LDP (mLDP) In-Band Signaling with Wildcards. IJ. Wijnands, Ed., E. Rosen, A. Gulko, U. Joorde, J. Tantsura. January 2015. (Format: TXT=36744 bytes) (Updates RFC6826, RFC7246) (Status: PROPOSED STANDARD) (DOI: 10.17487/RFC7438) [RFC6826] and [RFC7246] define the following Opaque Value TLVs: Transit IPv4 Source TLV, Transit IPv6 Source TLV, Transit VPNv4 Source TLV, and Transit VPNv6 Source TLV. The value field of each such TLV is divided into a number of subfields, one of which contains an IP source address, and one of which contains an IP group address. Per those documents, these fields must contain valid IP addresses. Procedures for the use of a wildcard group in the following TLVs (defined in [RFC6826] or [RFC7246]) are outside the scope of the current document: Transit IPv4 Bidir TLV, Transit IPv6 Bidir TLV, Transit VPNv4 Bidir TLV, and Transit VPNv6 Bidir TLV.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ sunset4 mailing list [email protected] https://www.ietf.org/mailman/listinfo/sunset4
