The Experts below are selected from a list of 86340 Experts worldwide ranked by ideXlab platform
D. Brungard - One of the best experts on this subject based on the ideXlab platform.
-
Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", RFC 4803
2007Co-Authors: D. BrungardAbstract:This memo provides information for the Internet community. It does not specify an Internet Standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). The Generalized Multi-Protocol Label Switching (GMPLS) suite of protocols has been defined to control different switching technologies as well as different applications. These include support for requesting Time Division Multiplexing (TDM) connections including Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) and Optical Transport Networks (OTNs). This document concentrates on the routing requirements placed on the GMPLS suite of protocols in order to support the capabilities and functionalities of an Automatically Switched Optical Network (ASON
-
Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base", RFC 4802
2007Co-Authors: D. BrungardAbstract:This memo provides information for the Internet community. It does not specify an Internet Standard of any kind. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2005). The Generalized Multi-Protocol Label Switching (GMPLS) suite of protocols has been defined to control different switching technologies as well as different applications. These include support for requesting Time Division Multiplexing (TDM) connections including Synchronous Optical Network (SONET)/Synchronous Digital Hierarchy (SDH) and Optical Transport Networks (OTNs). This document concentrates on the routing requirements placed on the GMPLS suite of protocols in order to support the capabilities and functionalities of an Automatically Switched Optical Network (ASON
M. Rose - One of the best experts on this subject based on the ideXlab platform.
-
Network Working Group Internet Draft: POP3
1994Co-Authors: J. Myers, M. RoseAbstract:its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a ‘‘working draft’ ’ or ‘‘work in progress‘‘. To learn the current status of any Internet-Draft, please check the 1id-abstracts.txt listing contained in the Internet-Drafts Shadow Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or munnari.oz.au. A revised version of this draft document will be submitted to the RFC editor as an Internet Standard for the Internet Community. Discussion and suggestions for improvement are requested. This document will expire before 15 Nov 1995. Distribution of this draft is unlimited. Overview This memo is a revision to RFC 1725, a Draft Standard. It makes the following changes from that document:- specifies a UID length limitation of one to 70 octets- specifies a status indicator length limitation of 512 octets, including the CRLF- clarifies that LIST with no arguments on an empty mailbox returns success- clarifies the security section to not imply the use of the USER command with the APOP command. Myers & Rose [Page 1] draft-myers-pop-pop3.txt POP3 November 1994 1
-
Connection: close Content-Type: text/plain Network Working Group Internet Draft: POP3
1994Co-Authors: Etag ", M. Rose, J. Myers, Dover Beach ConsultingAbstract:documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a ‘‘working draft’ ’ or ‘‘work in progress‘‘. To learn the current status of any Internet-Draft, please check the 1id-abstracts.txt listing contained in the Internet-Drafts Shadow Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or munnari.oz.au. A revised version of this draft document will be submitted to the RFC editor as an Internet Standard for the Internet Community. Discussion and suggestions for improvement are requested. This document will expire before 15 Nov 1995. Distribution of this draft is unlimited. Overview This memo is a revision to RFC 1725, a Draft Standard. It makes the following changes from that document:- clarifies that command keywords are case insensitve.- specifies that servers must send "+OK " and "-ERR " in upper case.- specifies that the initial greeting is a positive response, instead of any string which should be a positive response.- reverses the order of the examples in the USER and PASS commands, to reduce confusion. Myers & Rose [Page 1] draft-myers-pop-pop3-01.txt POP3 November 1994- clarifies that the PASS command may only be given immediately after a successful USER command.- specifies a UID length limitation of one to 70 octets.- specifies a status indicator length limitation of 512 octets, including the CRLF.- clarifies that LIST with no arguments on an empty mailbox returns success.- clarifies the security section to not imply the use of the USER command with the APOP command. 1
-
introduction to version 2 of the Internet Standard network management framework
RFC, 1993Co-Authors: J. Case, M. Rose, Keith Mccloghrie, S WaldbusserAbstract:The purpose of this document is to provide an overview of version 2 of the Internet-Standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [StandardS-TRACK]
-
General Principles and Policy Status of this Memo
1993Co-Authors: M. RoseAbstract:This memo provides information for the Internet community. It does not specify an Internet Standard. Distribution of this memo is unlimited. This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System [1,2]. This document is informational and applies only to those Internet sites that choose to register themselves within the tpc.int subdomain. The tpc.int subdomain is organized as a cooperative of the sites that provide access within the context of the subdomain. Policy for the subdomain is set by a board responsible to the cooperative. The primary purpose of the tpc.int subdomain is to provid
-
General Principles and Policy
1993Co-Authors: M. RoseAbstract:This memo provides information for the Internet community. It does not specify an Internet Standard. Distribution of this memo is unlimited. This document defines the initial principles of operation for the tpc.int subdomain, a collection of service listings accessible over the Internet infrastructure through an administered namespace contained within the Domain Name System [1,2]. This document is informational and applies only to those Internet sites that choose to register themselves within the tpc.int subdomain. The tpc.int subdomain is organized as a cooperative of the sites that provide access within the context of the subdomain. Policy for the subdomain is set by a board responsible to the cooperative. The primary purpose of the tpc.int subdomain is to provide transparent mapping between general-purpose computers on the Internet and special-purpose devices directly connected to the telephone network. Initially, a remote printing service is defined [3,4] which ties together G3-compatible facsimile devices on the telephone network with users of electronic mail in the Internet and associated message-handling domains connected to the Internet by applicationlayer gateways. It should be noted that remote printer gateways have long been technically feasible and have become an integral part of many individual networks. The tpc.int subdomain integrates individual sites into a common namespace, transforming remote printing from a single-site, value-added service into an integral transparent service in the global Internet
S. Vogelsang - One of the best experts on this subject based on the ideXlab platform.
-
Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation Service over MPLS (CEM) Encapsulation
2008Co-Authors: Andrew Malis, J. Brayley, J. Shirron, Eci Telecom Inc, L. Martini, S. VogelsangAbstract:This memo defines a Historic Document for the Internet community. It does not specify an Internet Standard of any kind. Distribution of this memo is unlimited. IESG Note The IESG thinks that this work is related to IETF work done in WG PWE3, but this does not prevent publishing. This document describes a historical method for encapsulating Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Path signals for transport across packet-switched networks (PSNs). The PSNs explicitly supported by this document include MPLS and IP. Note that RFC 4842 describes the Standards-track protocol for this functionality, and new implementations must use RFC 4842 rather than this document except when interoperability with older implementations is desired
-
Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Circuit Emulation over Packet (CEP)", RFC 4842
2007Co-Authors: Andrew Malis, J. Brayley, J. Shirron, Eci Telecom Inc, L. Martini, S. VogelsangAbstract:This memo defines a Historic Document for the Internet community. It does not specify an Internet Standard of any kind. Distribution of this memo is unlimited. IESG Note The IESG thinks that this work is related to IETF work done in WG PWE3, but this does not prevent publishing. This document describes a historical method for encapsulating Synchronous Optical Network/Synchronous Digital Hierarchy (SONET/SDH) Path signals for transport across packet-switched networks (PSNs). The PSNs explicitly supported by this document include MPLS and IP. Note that RFC 4842 describes the Standards-track protocol for this functionality, and new implementations must use RFC 4842 rather than this document except when interoperability with older implementation
R. Mcduff - One of the best experts on this subject based on the ideXlab platform.
-
Internet Engineering Task Force (IETF) Request for Comments: 6338
2011Co-Authors: V. Giralt, R. McduffAbstract:Definition of a Uniform Resource Name (URN) Namespace for the Schema for Academia (SCHAC) This document describes a Uniform Resource Name (URN) namespace for the Schema for Academia (SCHAC). The namespace described in this document is for naming persistent resources defined by the SCHAC participants internationally, their working groups, and other designated subordinates. The main use of this namespace will be for the creation of controlled vocabulary values for attributes in the SCHAC schema. These values will be associated with particular instances of persons or objects belonging to any of the SCHAC object classes. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained a
-
Definition of a Uniform Resource Name (URN) Namespace
2011Co-Authors: V. Giralt, R. McduffAbstract:for the Schema for Academia (SCHAC) This document describes a Uniform Resource Name (URN) namespace for the Schema for Academia (SCHAC). The namespace described in this document is for naming persistent resources defined by the SCHAC participants internationally, their working groups, and other designated subordinates. The main use of this namespace will be for the creation of controlled vocabulary values for attributes in the SCHAC schema. These values will be associated with particular instances of persons or objects belonging to any of the SCHAC object classes. Status of This Memo This document is not an Internet Standards Track specification; it is published for informational purposes. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained a
J. Case - One of the best experts on this subject based on the ideXlab platform.
-
Introduction and Applicability Statements for Internet-Standard Management Framework
2002Co-Authors: J. Case, R. Mundy, D. Partain, B. StewartAbstract:The purpose of this document is to provide an overview of the third version of the Internet-Standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This Framework is derived from and builds upon both the original Internet-Standard Management Framework (SNMPv1) and the second Internet-Standard Management Framework (SNMPv2).
-
Introduction to Version 3 of the Internet-Standard Network Management Framework
1999Co-Authors: J. Case, R. Mundy, D. Partain, B. StewartAbstract:The purpose of this document is to provide an overview of the third version of the Internet-Standard Management Framework, termed the SNMP version 3 Framework (SNMPv3). This Framework is derived from and builds upon both the original Internet-Standard Management Framework (SNMPv1) and the second Internet-Standard Management Framework (SNMPv2).
-
coexistence between version 1 and version 2 of the Internet Standard network management framework
RFC, 1993Co-Authors: J. Case, Keith Mccloghrie, Marshall T Rose, S WaldbusserAbstract:The purpose of this document is to describe coexistence between version 2 of the Internet-Standard Network Management Framework [1-6], termed the SNMP version 2 framework (SNMPv2), and the original Internet- Standard Network Management Framework (SNMPv1). [StandardS- TRACK]
-
introduction to version 2 of the Internet Standard network management framework
RFC, 1993Co-Authors: J. Case, M. Rose, Keith Mccloghrie, S WaldbusserAbstract:The purpose of this document is to provide an overview of version 2 of the Internet-Standard Network Management Framework, termed the SNMP version 2 framework (SNMPv2). [StandardS-TRACK]