@techreport {Briscoe11b:ecn-encap-guide_ID,
	title = {Guidelines for Adding Congestion Notification to Protocols that Encapsulate IP},
	number = {draft-ietf-tsvwg-ecn-encap-guidelines-08},
	year = {2017},
	note = {(Work in Progress)},
	publisher = {IETF},
	keywords = {Architecture, congestion, Control, Data Communication, Encapsulation, Explicit Notification, Internet, Layering, Management, Monitoring, networks, Protocol Engineering, QoS, Tunnels},
	url = {http://tools.ietf.org/html/draft-ietf-tsvwg-ecn-encap-guidelines},
	author = {Briscoe, Bob and Kaippallimalil, John and Thaler, Pat}
}
@techreport {Eastlake16:I-D-trill-ecn-support,
	title = {TRILL: ECN (Explicit Congestion Notification) Support},
	number = {draft-ietf-trill-ecn-support-02},
	year = {2017},
	note = {(Work in Progress)},
	month = {03/2017},
	publisher = {Internet Engineering Task Force},
	abstract = {Explicit congestion notification (ECN) allows a forwarding element to notify downstream devices, including the destination, of the onset of congestion without having to drop packets. This document extends this capability to TRILL switches, including integration with IP ECN.},
	keywords = {Architecture, congestion, Control, Data Communication, Encapsulation, Explicit Notification, Incremental Deployment, Internet, Layering, networks, Protocol Engineering, QoS, Tunnels},
	url = {http://tools.ietf.org/html/draft-ietf-trill-ecn-support},
	author = {Eastlake, Donald and Briscoe, Bob}
}
@techreport {25061,
	title = {Propagating Explicit Congestion Notification Across IP Tunnel Headers Separated by a Shim},
	number = {g-rfc6040update-shim-00},
	year = {2016},
	note = {(Work in Progress)},
	month = {11/2016},
	publisher = {Internet Engineering Task Force},
	abstract = {RFC 6040 on "Tunnelling of Explicit Congestion Notification" made the rules for propagation of ECN consistent for all forms of IP in IP tunnel.  This specification extends the scope of RFC 6040 to include tunnels where two IP headers are separated by a shim header that cannot stand alone.},
	keywords = {Architecture, congestion, Control, Data Communication, Encapsulation, Explicit Notification, Internet, Layering, Management, Monitoring, networks, Protocol Engineering, QoS, Tunnels},
	url = {http://tools.ietf.org/html/draft-briscoe-tsvwg-rfc6040update-shim},
	author = {Briscoe, Bob}
}
@techreport {Stein12:pwe3-congcons_ID,
	title = {Pseudowire Congestion Considerations},
	number = {RFC7893},
	year = {2016},
	month = {06/2016},
	publisher = {RFC Editor},
	keywords = {congestion, Control, Data Communication, Encapsulation, Fairness, Internet, Layering, networks, Protocol Engineering, Pseudowire, QoS, Standards, TDM, Tunnels},
	issn = {2070-1721},
	doi = {http://dx.doi.org/10.17487/RFC7893},
	url = {https://www.rfc-editor.org/rfc/rfc7893.txt},
	author = {Stein, Yaakov and Black, David and Briscoe, Bob}
}
@techreport {Manner09:GUT_ID,
	title = {Generic UDP Tunnelling (GUT)},
	number = {draft-manner-tsvwg-gut-02},
	year = {2010},
	note = {(Expired)},
	month = {07/2010},
	publisher = {Internet Engineering Task Force},
	type = {Internet Draft},
	keywords = {Architecture, Data Communication, Encapsulation, Endpoint Identification, Internet, Layering, NAT traversal, networks, Protocol Engineering, Tunnelling},
	url = {http://www.ietf.org/internet-drafts/draft-manner-tsvwg-gut-02.txt},
	author = {Manner, Jukka and Varis, Nuutti and Briscoe, Bob}
}
@techreport {Briscoe07b:ECN-tunnel,
	title = {Tunnelling of Explicit Congestion Notification},
	number = {6040},
	year = {2010},
	month = {11/2010},
	publisher = {RFC Editor},
	type = {Request for Comments},
	keywords = {Architecture, congestion, Control, Covert Channel, Data Communication, Encapsulation, Explicit Notification, Internet, Layering, Management, Monitoring, networks, Protocol Engineering, QoS, Security, Tunnels},
	url = {http://www.ietf.org/rfc/rfc6040.txt},
	author = {Briscoe, Bob}
}
