12.07.2015 Views

Network Working Group J. Reynolds Request for Comments: 1700 J ...

Network Working Group J. Reynolds Request for Comments: 1700 J ...

Network Working Group J. Reynolds Request for Comments: 1700 J ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

RFC <strong>1700</strong> Assigned Numbers October 199400ffreserved (compression inefficient)0201 802.1d Hello Packets0203 IBM Source Routing BPDU0205 DEC LANBridge100 Spanning Tree0231 Luxcom0233 Sigma <strong>Network</strong> Systems8001-801f Not Used - reserved [RFC1661]8021 Internet Protocol Control Protocol8023 OSI <strong>Network</strong> Layer Control Protocol8025 Xerox NS IDP Control Protocol8027 DECnet Phase IV Control Protocol8029 Appletalk Control Protocol802bNovell IPX Control Protocol802dreserved802freserved8031 Bridging NCP8033 Stream Protocol Control Protocol8035 Banyan Vines Control Protocol8037 reserved till 19938039 reserved803breserved803dMulti-Link Control Protocol803fNETBIOS Framing Control Protocol807d Not Used - reserved [RFC1661]8041 Cisco Systems Control Protocol8043 Ascom Timeplex8045 Fujitsu LBLB Control Protocol8047 DCA Remote Lan <strong>Network</strong> Control Protocol (RLNCP)8049 Serial Data Control Protocol (PPP-SDCP)804bSNA over 802.2 Control Protocol804dSNA Control Protocol804fIP6 Header Compression Control Protocol006fStampede Bridging Control Protocol80cf Not Used - reserved [RFC1661]80fbcompression on single link in multilink group control80fdCompression Control Protocol80ff Not Used - reserved [RFC1661]c021Link Control Protocolc023Password Authentication Protocolc025Link Quality Reportc027Shiva Password Authentication Protocolc029CallBack Control Protocol (CBCP)c081 Container Control Protocol [KEN]c223Challenge Handshake Authentication Protocolc281 Proprietary Authentication Protocol [KEN]<strong>Reynolds</strong> & Postel [Page 201]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!