< draft-acee-idr-lldp-peer-discovery-03.txt		draft-acee-idr-lldp-peer-discovery-04.txt >
	Network Working Group A. Lindem		Network Working Group A. Lindem
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Intended status: Standards Track K. Patel		Intended status: Standards Track K. Patel
	Expires: January 1, 2019 Arrcus, Inc		Expires: July 3, 2019 Arrcus, Inc
	S. Zandi		S. Zandi
	LinkedIn		LinkedIn
	J. Haas		J. Haas
	Juniper Networks, Inc		Juniper Networks, Inc
	X. Xu		X. Xu
	Huawei		Huawei
	June 30, 2018		December 30, 2018
	BGP Logical Link Discovery Protocol (LLDP) Peer Discovery		BGP Logical Link Discovery Protocol (LLDP) Peer Discovery
	draft-acee-idr-lldp-peer-discovery-03.txt		draft-acee-idr-lldp-peer-discovery-04.txt
	Abstract		Abstract
	Link Layer Discovery Protocol (LLDP) or IEEE 802.1AB is implemented		Link Layer Discovery Protocol (LLDP) or IEEE 802.1AB is implemented
	in networking equipment from many vendors. It is natural for IETF		in networking equipment from many vendors. It is natural for IETF
	protocols to avail this protocol for simple discovery tasks. This		protocols to avail this protocol for simple discovery tasks. This
	document describes how BGP would use LLDP to discover directly		document describes how BGP would use LLDP to discover directly
	connected and 2-hop peers when peering is based on loopback		connected and 2-hop peers when peering is based on loopback
	addresses.		addresses.
	skipping to change at page 1, line 42 ¶		skipping to change at page 1, line 42 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on January 1, 2019.		This Internet-Draft will expire on July 3, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 7, line 21 ¶		skipping to change at page 7, line 21 ¶
	is shown below.		is shown below.
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Type (3) | Length (4) | BGP Identifier |		| Type (3) | Length (4) | BGP Identifier |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| BGP Identifier |		| BGP Identifier |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Type The Sub-TLV Type value shall be f32.		Type The Sub-TLV Type value shall be 3.
	Length The Sub-TLV Length will be 4 octets.		Length The Sub-TLV Length will be 4 octets.
	BGP Identifier Local BGP Identifier (aka, BGP Router ID)		BGP Identifier Local BGP Identifier (aka, BGP Router ID)
	2.2.4. BGP Config OS-TLV - Session Group-ID Sub-TLV		2.2.4. BGP Config OS-TLV - Session Group-ID Sub-TLV
	The BGP Config OS-TLV Session Group-ID Sub-TLV is an opaque 4-octet		The BGP Config OS-TLV Session Group-ID Sub-TLV is an opaque 4-octet
	value that is used to represent a category of BGP session that is		value that is used to represent a category of BGP session that is
	supported on the interface. The format of the Session Group-ID Sub-		supported on the interface. The format of the Session Group-ID Sub-
	skipping to change at page 15, line 52 ¶		skipping to change at page 15, line 52 ¶
	[TCP-MD5] Heffernan, A., "TCP MD5 Signature Option", RFC 2385,		[TCP-MD5] Heffernan, A., "TCP MD5 Signature Option", RFC 2385,
	August 1998.		August 1998.
	[YANG-KEY-CHAIN]		[YANG-KEY-CHAIN]
	Lindem, A., Qu, Y., Yeung, D., Chen, I., and J. Zhang,		Lindem, A., Qu, Y., Yeung, D., Chen, I., and J. Zhang,
	"YANG Data Model for Key Chains", RFC 8177, June 2017.		"YANG Data Model for Key Chains", RFC 8177, June 2017.
	Appendix A. Acknowledgments		Appendix A. Acknowledgments
			Thanks to Sujay Gupta for review and comments.
	The RFC text was produced using Marshall Rose's xml2rfc tool.		The RFC text was produced using Marshall Rose's xml2rfc tool.
	Authors' Addresses		Authors' Addresses
	Acee Lindem		Acee Lindem
	Cisco Systems		Cisco Systems
	301 Midenhall Way		301 Midenhall Way
	Cary, NC 27513		Cary, NC 27513
	USA		USA
End of changes. 6 change blocks.
	5 lines changed or deleted		7 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/