Feb :33 draft-glenn-id-notification-mib-04.txt Page 1

Size: px
Start display at page:

Download "Feb :33 draft-glenn-id-notification-mib-04.txt Page 1"

Transcription

1 Feb :33 Page 1 ID Message Exchange Format Working Group Glenn Mansfield INTERNET-DRAFT Cyber Solutions Inc. November 20,2000 Status of this Memo Intrusion Detection Message MIB <> This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and 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 and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet- Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice Copyright (C) The Internet Society (2000). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines the contents of messages that will be exchanged among intrusion detection systems when an intrusion is detetcted. Expires: May 19, 2001 [Page 1]

2 Feb :33 Page 2 Table of Contents 1. The SNMP Network Management Framework The Intrusion Detection Message Exchange Model MIB Model for ID Message Exchanges MIB design The Intrusion Detection Message MIB Intellectual Property Acknowledgements References...38 Security Considerations...40 Authors Addresses...41 Full Copyright Statement...42 Expires: May 19, 2001 [Page 2]

3 Feb :33 Page 3 1. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: o o o o An overall architecture, described in RFC 2571 [RFC2571]. Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 [RFC2580]. Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A second version of the SNMP message protocol, which is not an Internet standards track protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version of the message protocol is called SNMPv3 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is described in STD 15, RFC 1157 [RFC1157]. A second set of protocol operations and associated PDU formats is described in RFC 1905 [RFC1905]. o A set of fundamental applications described in RFC 2573 [RFC2573] and the view-based access control mechanism described in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine Expires: May 19, 2001 [Page 3]

4 Feb :33 Page 4 readable information is not considered to change the semantics of the MIB. 2. The Intrusion detection model. An Intrusion Detection system (ID1) generally comprises an Analyzer which scans Data Sources for signs of intrusions. When it detects a sign or a signature, an event occurs. The analyzer then sends a Message or Alert to the Manager(s). Managers in turn may exchange Messages or Alerts for cooperative or collaborative purposes. ID Message Exchange Model =========================... ID1 : : : : Message : DataSource Analyzer > Manager :... Alert : : Event : X : ID1 : Message/ ID2 : Alert : : : X : : : Manager : : : : Expires: May 19, 2001 [Page 4]

5 Feb :33 Page 5 3. MIB Model for ID Message Exchanges. In Intrusion detection and management, the communication between the different components of the system will essentially be event based. Presumably, some components (analysers or agents) will be assigned the tasks for watching some data-sources and looking out for signs of (attepmpted) intrusions or attacks. In case any such sign is detected it is brought to the notice of the Manager. The Manager will then take the appropriate action which may involve relaying the notification and/or carrying out further investigation by talking to peers, higher level managers and/or the entity that originated the notification. The investigation carried out by the manager will possibly involve getting o more information on some of the fields that are present in the messages from the agents. [Maybe using Http, ftp ] o more host-related information on the circumstances under which the intrusion/attack was detected - this may involve fetching further information from the various MIBs of the entity that originated the notification. o more network-related information on the circumstances under which the intrusion/attack was detected - this may involve fetching further information from the various MIBs of the relevant network entities in the network The notification to the manager will take the form of an informrequest. There may be several types of notifications. The constraint on a notification is its size. It is desirable that the packet carrying the notification is not fragmented at the IP level. The MIB defined in this document covers the portion which is specific to the Intrusion Detection Message itself. The other components of information that may be of relevance to the investigation will probably be found in the various MIBs defined. If they are absent then newer MIBs will have to be defined. Expires: May 19, 2001 [Page 5]

6 Feb :33 Page 6 4. MIB design. The basic design principle has been to keep the MIB as simple as possible. The generic requirements on the ID Alert messages are o ID Alerts should contain the minimum information required by the manager to assess the situation correctly and to take appropriate defensive or investigative steps. o ID Alerts, if carried in UDP datagrams, should not be too large as to require IP fragmentation. [If SNMP is used as the the application protocol, some managers may not accept SNMP-PDUs that are larger than 484 bytes.] An additional requirement is to retain the similarity of this MIB with the XML-DTD as the primary objective of this MIB is to map Alerts in XML to corresponding SMI objects which can be communicated to SNMP-entities. The MIB comprises of the idalertobjects described below. o The idalertobjects subtree defines the objects that are used in the notifications. This contains objects of three categories (i) Objects pertaining to the Alert originator (ii) A table in which each row represents details pertaining to an Alert (iii)supplementary tables - idtimetable - iddtimetable - idantimetable - idclassificationtable - idsourcetable - idtargettable - idtoolalerttable - idoverflowalerttable - idcorrelationalerttable - idadditionaldatatable - idargumentstable - idusertable - idprocesstable - idaddresstable - idnodetable - idanalyzertable - idenvironmenttable - idservicetable Expires: May 19, 2001 [Page 6]

7 Feb :33 Page 7 5. The Intrusion Detection Message MIB. INTRUSION-DETECTION-ALERT-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, Counter32, Gauge32, OBJECT-TYPE, OBJECT-IDENTITY, IpAddress, mib-2 FROM SNMPv2-SMI DateAndTime, TimeStamp FROM SNMPv2-TC SnmpAdminString FROM SNMP-FRAMEWORK-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF URLString FROM NETWORK-SERVICES-MIB; idmib MODULE-IDENTITY LAST-UPDATED " Z" -- 20th November 2000 ORGANIZATION "IETF Intrusion Detection Message Exchange Format Working Group" CONTACT-INFO " Glenn Mansfield Postal: Cyber Solutions Inc , Minami Yoshinari Aoba-ku, Sendai, Japan Tel: Fax: glenn@cysols.com Working Group idwg-public@zurich.ibm.com To subscribe: idwg-public-request@zurich.ibm.com" " The MIB for Intrusion Detection Messages." REVISION " Z" -- 25th July 2000 "First draft of the idmib" REVISION " Z" -- 16th November 2000 "Revised to reflect the structure of the objects in the XML-DTD. Syntactic nits removed." REVISION " Z" -- 20th November 2000 "Syntactic nits removed." Expires: May 19, 2001 [Page 7]

8 Feb :33 Page 8 ::= { mib-2 xxx -- to be assigned by IANA idalertobjects OBJECT-IDENTITY " This is the base object for the objects used in the alert notifications." ::= {idmib 1 -- idalerttable: The Table of Alerts. Each row represents an Alert. -- AlertID is the key to the table idalerttable OBJECT-TYPE SYNTAX SEQUENCE OF IdAlertEntry " Each row of this table contains information about an alert indexed by idalertid." ::= { idalertobjects 1 idalertentry OBJECT-TYPE SYNTAX IdAlertEntry " Entry containing information pertaining to an alert." INDEX { idalertid ::= { idalerttable 1 IdAlertEntry ::= SEQUENCE { idalertversion idalertid idalertimpact INTEGER idalertversion OBJECT-TYPE " The version of the class hierarchy used in defining the alert." ::= {idalertentry 1 Expires: May 19, 2001 [Page 8]

9 Feb :33 Page 9 idalertid OBJECT-TYPE SYNTAX INTEGER ( ) " The AlertID uniquely identifies each alert generated by an analyzer." ::= {idalertentry 2 -- will be enumerated to represent the allowed types idalertimpact OBJECT-TYPE SYNTAX INTEGER "An indication of the impact of the (potential) impact of the event on the system." ::= {idalertentry 3 idtimetable OBJECT-TYPE SYNTAX SEQUENCE OF IdTimeEntry " Each row of this table contains information about the time of an alert indexed by idalertid." ::= { idalertobjects 2 idtimeentry OBJECT-TYPE SYNTAX IdTimeEntry " Entry containing information pertaining to the time an alert was generated." INDEX { idalertid ::= { idtimetable 1 IdTimeEntry ::= SEQUENCE { idtimeoffset idtimentpstamp idtimedate idtimetime SnmpAdminString Expires: May 19, 2001 [Page 9]

10 Feb :33 Page 10 idtimeoffset OBJECT-TYPE " Specifies the offset from Coordinated Universal Time UTC, formerly referred to as Greenwich Mean Time that the <date> and <time> elements represent." ::= {idtimeentry 1 idtimentpstamp OBJECT-TYPE " The NTP timestamp." ::= {idtimeentry 2 idtimedate OBJECT-TYPE " The Date. " ::= {idtimeentry 3 idtimetime OBJECT-TYPE " The Time." ::= {idtimeentry 4 iddtimetable OBJECT-TYPE SYNTAX SEQUENCE OF IdTimeEntry " Each row of this table contains information about the detection time of the event that caused the alert." ::= {idalertobjects 3 iddtimeentry OBJECT-TYPE SYNTAX IdDTimeEntry Expires: May 19, 2001 [Page 10]

11 Feb :33 Page 11 " Entry containing information pertaining to the time an event was detected." INDEX {idalertid ::= {iddtimetable 1 IdDTimeEntry ::= SEQUENCE { iddtimeoffset iddtimentpstamp iddtimedate iddtimetime SnmpAdminString iddtimeoffset OBJECT-TYPE " Specifies the offset from Coordinated Universal Time UTC, that the idtimedate and idtimetime elements it represents." ::= {iddtimeentry 1 iddtimentpstamp OBJECT-TYPE " The NTP timestamp." ::= { iddtimeentry 2 iddtimedate OBJECT-TYPE " The Date. " ::= { iddtimeentry 3 iddtimetime OBJECT-TYPE Expires: May 19, 2001 [Page 11]

12 Feb :33 Page 12 " The Time." ::= { iddtimeentry 4 idantimetable OBJECT-TYPE SYNTAX SEQUENCE OF IdAnTimeEntry " A row of this table contains information about the current time on the Analyzer. This table will have only one row." ::= { idalertobjects 4 idantimeentry OBJECT-TYPE SYNTAX IdAnTimeEntry " Entry containing information pertaining to the time an alert was generated." INDEX { idalertid ::= { idantimetable 1 IdAnTimeEntry ::= SEQUENCE { idantimeoffset idantimentpstamp idantimedate idantimetime SnmpAdminString idantimeoffset OBJECT-TYPE " Specifies the offset from Coordinated Universal Time UTC, formerly referred to as Greenwich Mean Time, that the idantimedate and idantimetime elements represent." ::= {idantimeentry 1 idantimentpstamp OBJECT-TYPE Expires: May 19, 2001 [Page 12]

13 Feb :33 Page 13 " The NTP timestamp." ::= {idantimeentry 2 idantimedate OBJECT-TYPE " The Date. " ::= {idantimeentry 3 idantimetime OBJECT-TYPE " The Time." ::= {idantimeentry 4 idclassificationtable OBJECT-TYPE SYNTAX SEQUENCE OF IdClassificationEntry " Each row of this table contains information about the classification of an alert and is indexed by idalertid and the idclassification Index." ::= { idalertobjects 5 idclassificationentry OBJECT-TYPE SYNTAX IdClassificationEntry " Entry containing information pertaining to the classification of the alert." INDEX { idalertid, idclassificationindex ::= { idclassificationtable 1 IdClassificationEntry ::= SEQUENCE { idclassificationindex idclassificationorigin idclassificationname idclassificationurl Expires: May 19, 2001 [Page 13]

14 Feb :33 Page 14 SnmpAdminString idclassificationindex OBJECT-TYPE SYNTAX INTEGER ( ) "An index that uniquely identifies the row in the table." ::= {idclassificationentry 1 idclassificationorigin OBJECT-TYPE " The NTP timestamp." ::= {idclassificationentry 2 idclassificationname OBJECT-TYPE " The Date. " ::= {idclassificationentry 3 idclassificationurl OBJECT-TYPE " The Time." ::= {idclassificationentry 4 idsourcetable OBJECT-TYPE SYNTAX SEQUENCE OF IdSourceEntry " Each row of this table contains information about the source of an attack for which the alert is being raised." ::= { idalertobjects 6 idsourceentry OBJECT-TYPE SYNTAX IdSourceEntry Expires: May 19, 2001 [Page 14]

15 Feb :33 Page 15 " Entry pertaining to a source of the attack." INDEX { idalertid, idsourceindex ::= { idsourcetable 1 IdSourceEntry ::= SEQUENCE { idsourceindex idsourcespoofed idsourceid SnmpAdminString idsourceindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the host entry in the table." ::= {idsourceentry 1 idsourcespoofed OBJECT-TYPE SYNTAX INTEGER { unknown(0), spoofed(1), -- do not know if spoofed or not -- this is not the true source -- this is the true source notspoofed(2) " An indication of whether the analyzer believes this to be the true source of the event." ::= {idsourceentry 2 idsourceid OBJECT-TYPE " An Identifier for the source " ::= {idsourceentry 3 idtargettable OBJECT-TYPE SYNTAX SEQUENCE OF IdTargetEntry Expires: May 19, 2001 [Page 15]

16 Feb :33 Page 16 " Each row of this table contains information about the target of the attack for which the alert is being raised." ::= { idalertobjects 7 idtargetentry OBJECT-TYPE SYNTAX IdTargetEntry " Entry containing information pertaining to the time an alert was generated." INDEX { idalertid, idtargetindex ::= { idtargettable 1 IdTargetEntry ::= SEQUENCE { idtargetindex idtargetdecoy idtargetid SnmpAdminString idtargetindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the target entry in the table." ::= {idtargetentry 1 idtargetdecoy OBJECT-TYPE SYNTAX INTEGER { unknown(0), decoy(1), -- no information available -- this is not the true target -- this is the true target notdecoy(2) " An indication of whether the analyzer believes this to be the true target of the event." ::= {idtargetentry 2 Expires: May 19, 2001 [Page 16]

17 Feb :33 Page 17 idtargetid OBJECT-TYPE " An Identifier for the target " ::= {idtargetentry 3 idtoolalerttable OBJECT-TYPE SYNTAX SEQUENCE OF IdToolAlertEntry " Each row of this table contains information tool used in the attacks." ::= { idalertobjects 8 idtoolalertentry OBJECT-TYPE SYNTAX IdToolAlertEntry " Entry containing information about the tool which was used in the attack." INDEX { idalertid, idtoolalertidindex ::= { idtoolalerttable 1 IdToolAlertEntry ::= SEQUENCE { idtoolalertidindex idtoolalertname idtoolalertcommand idtoolalertids SnmpAdminString idtoolalertidindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the entry in the table." ::= {idtoolalertentry 1 Expires: May 19, 2001 [Page 17]

18 Feb :33 Page 18 idtoolalertname OBJECT-TYPE " The name of the tool used in the attack." ::= {idtoolalertentry 2 idtoolalertcommand OBJECT-TYPE " The command or operation the tool was asked to perform." ::= {idtoolalertentry 3 idtoolalertids OBJECT-TYPE " The alerts that have been identified as being related to the tool name." ::= {idtoolalertentry 4 idoverflowalerttable OBJECT-TYPE SYNTAX SEQUENCE OF IdOverflowAlertEntry " Each row of this table contains information about the buffer-overflow types of attacks." ::= { idalertobjects 9 idoverflowalertentry OBJECT-TYPE SYNTAX IdOverflowAlertEntry " Entry containing buffer-overflow related information for the corresponding attack." INDEX { idalertid ::= { idoverflowalerttable 1 IdOverflowAlertEntry ::= SEQUENCE { idoverflowalertprogram Expires: May 19, 2001 [Page 18]

19 Feb :33 Page 19 idoverflowalertsize idoverflowalertbuffer SnmpAdminString idoverflowalertprogram OBJECT-TYPE " The program that the overflow attacker attempted to run." ::= {idoverflowalertentry 1 idoverflowalertsize OBJECT-TYPE " The size, in bytes, of the overflowing buffer." ::= {idoverflowalertentry 2 idoverflowalertbuffer OBJECT-TYPE "Some or all of the data that was sent to the program." ::= {idoverflowalertentry 3 idcorrelationalerttable OBJECT-TYPE SYNTAX SEQUENCE OF IdCorrelationAlertEntry " Contains the list of alerts(indexed by idcorrelationindex) which were correlated to generate the present alert (indexed by idalertid)." ::= { idalertobjects 10 idcorrelationalertentry OBJECT-TYPE SYNTAX IdCorrelationAlertEntry " One of the alerts that was used in the correlation to generate the present alert indexed by idalertid." INDEX { idalertid Expires: May 19, 2001 [Page 19]

20 Feb :33 Page 20 ::= { idcorrelationalerttable 1 IdCorrelationAlertEntry ::= SEQUENCE { idcorrelationalertindex idcorrelationalertids SnmpAdminString idcorrelationalertindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the CorrelationAlert entry in the table." ::= {idcorrelationalertentry 1 idcorrelationalertids OBJECT-TYPE " List of alertids that are correlated." ::= {idcorrelationalertentry 2 idadditionaldatatable OBJECT-TYPE SYNTAX SEQUENCE OF IdAdditionalDataEntry " Each row of this table contains additional information related to the alert that is being raised." ::= { idalertobjects 11 idadditionaldataentry OBJECT-TYPE SYNTAX IdAdditionalDataEntry " Additional information corresponding to the alert that has been raised." INDEX { idalertid, idadditionaldataindex ::= { idadditionaldatatable 1 IdAdditionalDataEntry ::= SEQUENCE { idadditionaldataindex Expires: May 19, 2001 [Page 20]

21 Feb :33 Page 21 idadditionaldatatype idadditionaldatameaning SnmpAdminString idadditionaldataindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index that along with the Alert-ID uniquely identifies the row in the table." ::= {idadditionaldataentry 1 idadditionaldatatype OBJECT-TYPE "The type of the data in this element. " ::= {idadditionaldataentry 2 idadditionaldatameaning OBJECT-TYPE " A string that describes the meaning of the data in this element. These strings will be implementation dependent." ::= {idadditionaldataentry 3 idargumentstable OBJECT-TYPE SYNTAX SEQUENCE OF IdArgumentsEntry " Each row of this table contains information about the arguments used in the process indexed by idtargetindex." ::= { idalertobjects 12 idargumentsentry OBJECT-TYPE SYNTAX IdArgumentsEntry Expires: May 19, 2001 [Page 21]

22 Feb :33 Page 22 " A row containing one element of the argument information." INDEX { idalertid, idargumentssdtype, idargumentsprocindex ::= { idargumentstable 1 IdArgumentsEntry ::= SEQUENCE { idargumentssdtype -- Source/Destination idargumentsprocindex idarguments SnmpAdminString idargumentssdtype OBJECT-TYPE SYNTAX INTEGER { source(1), destination(2), -- process is on Node of type source -- process is on Node of type destination -- process is on Node of type analyzer analyzer(3) " An enumeration of the type of the node on which the referenced process is running." ::= {idargumentsentry 1 idargumentsprocindex OBJECT-TYPE " An index to identify the process." ::= {idargumentsentry 2 idarguments OBJECT-TYPE " The list of the arguments. " ::= {idargumentsentry 3 idusertable OBJECT-TYPE SYNTAX SEQUENCE OF IdUserEntry Expires: May 19, 2001 [Page 22]

23 Feb :33 Page 23 "The table containing information about users.." ::= { idalertobjects 13 iduserentry OBJECT-TYPE SYNTAX IdUserEntry "A row containing the details of a user" INDEX { idalertid, idusersdtype, iduserindex ::= { idusertable 1 IdUserEntry ::= SEQUENCE { idusersdtype iduserindex iduserident idusername iduseruid idusergroup idusergid iduserserial SnmpAdminString idusersdtype OBJECT-TYPE SYNTAX INTEGER { source(1), destination(2), -- user is on Node of type source -- user is on Node of type destination -- user is on Node of type analyzer analyzer(3) " An enumeration of the type of the node on which the referenced user exists." ::= { iduserentry 1 iduserindex OBJECT-TYPE SYNTAX INTEGER ( ) Expires: May 19, 2001 [Page 23]

24 Feb :33 Page 24 " An index uniquely identifying the user entry in the table." ::= { iduserentry 2 iduserident OBJECT-TYPE " The ID of the user." ::= { iduserentry 3 idusername OBJECT-TYPE " The name of the user." ::= { iduserentry 4 iduseruid OBJECT-TYPE " The UID of the user." ::= { iduserentry 5 idusergroup OBJECT-TYPE " The group of the user." ::= { iduserentry 6 idusergid OBJECT-TYPE " The gid of the user." ::= { iduserentry 7 Expires: May 19, 2001 [Page 24]

25 Feb :33 Page 25 iduserserial OBJECT-TYPE " The serial number of the user." ::= { iduserentry 8 idprocesstable OBJECT-TYPE SYNTAX SEQUENCE OF IdProcessEntry " A Table containing details of processes. " ::= { idalertobjects 14 idprocessentry OBJECT-TYPE SYNTAX IdProcessEntry "Each row contains details of a process indexed by idprocessindex on a node indexed by idnodeindex of type given by idprocesssdtype related to the alert indexed by idalertid." INDEX { idalertid, idprocesssdtype, idnodeindex, idprocessindex ::= { idprocesstable 1 IdProcessEntry ::= SEQUENCE { idprocesssdtype idprocessindex idprocessid idprocessname idprocesspid idprocesspath SnmpAdminString idprocesssdtype OBJECT-TYPE SYNTAX INTEGER { source(1), destination(2), analyzer(3) -- The process is running on a source -- The process is running on a destination -- The process is running on an analyzer Expires: May 19, 2001 [Page 25]

26 Feb :33 Page 26 " An enumeration of the type of the node on which the referenced process is running." ::= { idprocessentry 1 idprocessindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the process entry in the table." ::= { idprocessentry 2 idprocessid OBJECT-TYPE " The ID of the process." ::= { idprocessentry 3 idprocessname OBJECT-TYPE " The name of the process." ::= { idprocessentry 4 idprocesspid OBJECT-TYPE " The PID of the process." ::= { idprocessentry 5 idprocesspath OBJECT-TYPE " The absolute path of the process." Expires: May 19, 2001 [Page 26]

27 Feb :33 Page 27 ::= { idprocessentry 6 idaddresstable OBJECT-TYPE SYNTAX SEQUENCE OF IdAddressEntry "A Table containing address entries. " ::= { idalertobjects 15 idaddressentry OBJECT-TYPE SYNTAX IdAddressEntry " A row containing the address details. " INDEX { idaddresstype, idaddresstypeindex, idaddressindex ::= { idaddresstable 1 IdAddressEntry ::= SEQUENCE { idaddresstype -- source, target, user idaddresstypeindex -- idsourceindex, idtargetindex iduserindex idaddressindex idaddressid idaddresscategory idaddressaddress idaddressnetmask IpAddress idaddresstype OBJECT-TYPE SYNTAX INTEGER { source(1), -- Source type destination(2), -- Destination type analyzer(3), -- Analyzer user (4) -- User " An enumeration of the node type - this may be a source node a destination node or just Expires: May 19, 2001 [Page 27]

28 Feb :33 Page 28 an analyzer." ::= {idaddressentry 1 idaddresstypeindex OBJECT-TYPE SYNTAX INTEGER { source(1), -- Source type destination(2), -- Destination type analyzer(3), -- Analyzer user (4) -- User " An enumeration of the node type - this may be a source node a destination node or just an analyzer." ::= {idaddressentry 2 idaddressindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the node entry in the table." ::= {idaddressentry 3 idaddressid OBJECT-TYPE " An Identifier for the node " ::= {idaddressentry 4 idaddresscategory OBJECT-TYPE " A category for the node " ::= {idaddressentry 5 idaddressaddress OBJECT-TYPE Expires: May 19, 2001 [Page 28]

29 Feb :33 Page 29 " The address." ::= {idaddressentry 6 idaddressnetmask OBJECT-TYPE SYNTAX IpAddress " The mask of the address." ::= {idaddressentry 7 idnodetable OBJECT-TYPE SYNTAX SEQUENCE OF IdNodeEntry "A table containing details of nodes related to alerts. " ::= { idalertobjects 16 idnodeentry OBJECT-TYPE SYNTAX IdNodeEntry "A row pertaining to one node " INDEX { idalertid, idnodeindextype, idnodeindex ::= { idnodetable 1 IdNodeEntry ::= SEQUENCE { idnodeindextype idnodeindex idnodeid idnodecategory idnodename idnodelocation SnmpAdminString idnodeindextype OBJECT-TYPE SYNTAX INTEGER { source(1), destination(2), -- no information available -- this is not the true target Expires: May 19, 2001 [Page 29]

30 Feb :33 Page 30 analyzer(3) -- this is the true target " An enumeration of the node type - this may be a source node a destination node or just an analyzer." ::= {idnodeentry 1 idnodeindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the node entry in the table." ::= {idnodeentry 2 idnodeid OBJECT-TYPE " An Identifier for the node " ::= {idnodeentry 3 idnodecategory OBJECT-TYPE " An category for the node " ::= {idnodeentry 4 idnodename OBJECT-TYPE " An name for the node " ::= {idnodeentry 5 idnodelocation OBJECT-TYPE Expires: May 19, 2001 [Page 30]

31 Feb :33 Page 31 " The location of the node " ::= {idnodeentry 6 idanalyzertable OBJECT-TYPE SYNTAX SEQUENCE OF IdAnalyzerEntry " A table containing the list of analyzers serviced by this MIB." ::= { idalertobjects 17 idanalyzerentry OBJECT-TYPE SYNTAX IdAnalyzerEntry " A row containing details of an Analyzer" INDEX { idanalyzerindex ::= { idanalyzertable 1 IdAnalyzerEntry ::= SEQUENCE { idanalyzerindex idanalyzerid idanalyzernodeindex idanalyzerprocessindex INTEGER idanalyzerindex OBJECT-TYPE SYNTAX INTEGER ( ) " An Index to uniquely identify the Analyzer in this table." ::= {idanalyzerentry 1 idanalyzerid OBJECT-TYPE " An identifier to uniquely identify the Analyzer in the domain." Expires: May 19, 2001 [Page 31]

32 Feb :33 Page 32 ::= {idanalyzerentry 2 idanalyzernodeindex OBJECT-TYPE SYNTAX INTEGER ( ) " An Index pointing to the corresponding Node in the Node Table." ::= {idanalyzerentry 3 idanalyzerprocessindex OBJECT-TYPE SYNTAX INTEGER ( ) " An Index pointing to the corresponding process in the process table." ::= {idanalyzerentry 4 idenvironmenttable OBJECT-TYPE SYNTAX SEQUENCE OF IdEnvironmentEntry " Each row of this table contains information about the environment variables used in the process indexed by idtargetindex." ::= { idalertobjects 18 idenvironmententry OBJECT-TYPE SYNTAX IdEnvironmentEntry "." INDEX { idalertid, idprocessindex, idenvironmentindex ::= { idenvironmenttable 1 IdEnvironmentEntry ::= SEQUENCE { idenvironmentindex idenvironment SnmpAdminString idenvironmentindex OBJECT-TYPE Expires: May 19, 2001 [Page 32]

33 Feb :33 Page 33 SYNTAX INTEGER ( ) " An index uniquely identifying the process entry in the table." ::= { idenvironmententry 2 idenvironment OBJECT-TYPE " The ID of the process." ::= { idenvironmententry 3 idservicetable OBJECT-TYPE SYNTAX SEQUENCE OF IdServiceEntry " Each row of this table contains information about the services that have been targeted.." ::= { idalertobjects 19 idserviceentry OBJECT-TYPE SYNTAX IdServiceEntry "." INDEX { idalertid, idtargetindex, idserviceindex ::= { idservicetable 1 IdServiceEntry ::= SEQUENCE { idserviceindex idserviceid idservicename idservicedport idservicesport idserviceprotocol Expires: May 19, 2001 [Page 33]

34 Feb :33 Page 34 idserviceportlist SnmpAdminString idserviceindex OBJECT-TYPE SYNTAX INTEGER ( ) " An index uniquely identifying the process entry in the table." ::= { idserviceentry 1 idserviceid OBJECT-TYPE " The ID of the service." ::= { idserviceentry 2 idservicename OBJECT-TYPE " The name of the service." ::= { idserviceentry 3 idservicedport OBJECT-TYPE " The list of destination ports." ::= { idserviceentry 4 idservicesport OBJECT-TYPE " The list of source ports." ::= { idserviceentry 5 idserviceprotocol OBJECT-TYPE Expires: May 19, 2001 [Page 34]

35 Feb :33 Page 35 " The protocol used by the service." ::= { idserviceentry 6 idserviceportlist OBJECT-TYPE " The list of service related ports." ::= { idserviceentry 7 Expires: May 19, 2001 [Page 35]

36 Feb :33 Page Conformance information -- [TBD] END Expires: May 19, 2001 [Page 36]

37 Feb :33 Page Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF s procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 7. Acknowledgements This draft is the product of discussions and deliberations carried out in the IETF intrusion detection message exchange format working group (ietf-idwg-wg). Expires: May 19, 2001 [Page 37]

38 Feb :33 Page 38 References [RFC2571] [RFC1155] [RFC1212] [RFC1215] [RFC2578] [RFC2579] [RFC2580] [RFC1157] [RFC1901] [RFC1906] [RFC2572] [RFC2574] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999 Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990 Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991 M. Rose, "A Convention for Defining Traps for use with the SNMP", RFC 1215, March 1991 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", STD 15, RFC 1157, May Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduction to Community-based SNMPv2", RFC 1901, January Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1906, January Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2572, April 1999 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2574, April 1999 Expires: May 19, 2001 [Page 38]

39 Feb :33 Page 39 [RFC1905] [RFC2573] [RFC2575] [RFC2570] [INETMIB] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2573, April 1999 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model (VACM) for the Simple Network Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 of the Internet-standard Network Management Framework", RFC 2570, April work in progress. Expires: May 19, 2001 [Page 39]

40 Feb :33 Page 40 Security Considerations There are management objects defined in this MIB that have a MAX- ACCESS clause of read-write and read-create. There is the risk that an intruder can alter or create any management objects of this MIB via direct SNMP SET operations. So, care must be taken to put in place the security provisions of SNMP for authentication and access control. Not all versions of SNMP provide features for such a secure environment. SNMPv1 by itself is such an insecure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET (read) and SET (write) the objects in this MIB. It is strongly recommended that the implementors consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2274 [RFC2274] and the View-based Access Control Model RFC 2275 [RFC2275] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them. Expires: May 19, 2001 [Page 40]

41 Feb :33 Page 41 Authors Addresses Glenn Mansfield Cyber Solutions Inc Minami Yoshinari Aoba-ku, Sendai Japan Phone: Expires: May 19, 2001 [Page 41]

42 Feb :33 Page 42 Full Copyright statement "Copyright (C) The Internet Society (date). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implmentation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE." Expires: May 19, 2001 [Page 42]

43 Feb :33 Page 43

Feb :33 draft-glenn-id-sensor-alert-mib-01.txt Page 1

Feb :33 draft-glenn-id-sensor-alert-mib-01.txt Page 1 Feb 15 2001 17:33 Page 1 ID Message Exchange Format Working Group INTERNET-DRAFT Glenn Mansfield Cyber Solutions Inc. Dipankar Gupta Hewlett Packard Company November 20 2000 Status of this Memo Intrusion

More information

Network Working Group. Category: Standards Track Independent Consultant M. Ellison, Ed. Ellison Software Consulting, Inc.

Network Working Group. Category: Standards Track Independent Consultant M. Ellison, Ed. Ellison Software Consulting, Inc. Network Working Group Request For Comments: 2742 Category: Standards Track L. Heintz Cisco Systems S. Gudur Independent Consultant M. Ellison, Ed. Ellison Software Consulting, Inc. January 2000 Definitions

More information

Author of previous version: B. Stewart November 2000

Author of previous version: B. Stewart November 2000 Network Working Group Request for Comments: 3014 Category: Standards Track Editor of this version: R. Kavasseri Cisco Systems, Inc. Author of previous version: B. Stewart November 2000 Notification Log

More information

Network Working Group Request for Comments: 2667 Category: Standards Track August 1999

Network Working Group Request for Comments: 2667 Category: Standards Track August 1999 Network Working Group D. Thaler Request for Comments: 2667 Microsoft Category: Standards Track August 1999 Status of this Memo IP Tunnel MIB This document specifies an Internet standards track protocol

More information

Procket Networks D. Thaler Microsoft October 2000

Procket Networks D. Thaler Microsoft October 2000 Network Working Group Request for Comments: 2932 Category: Standards Track K. McCloghrie cisco Systems D. Farinacci Procket Networks D. Thaler Microsoft October 2000 IPv4 Multicast Routing MIB Status of

More information

Category: Standards Track Nortel Networks S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig June 2000

Category: Standards Track Nortel Networks S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig June 2000 Network Working Group Request for Comments: 2851 Category: Standards Track M. Daniele Compaq Computer Corporation B. Haberman Nortel Networks S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig

More information

Avaya Inc. K.C. Norseth L-3 Communications December 2002

Avaya Inc. K.C. Norseth L-3 Communications December 2002 Network Working Group Request for Comments: 3433 Category: Standards Track A. Bierman Cisco Systems, Inc. D. Romascanu Avaya Inc. K.C. Norseth L-3 Communications December 2002 Status of this Memo Entity

More information

Network Working Group. Category: Standards Track September 2003

Network Working Group. Category: Standards Track September 2003 Network Working Group B. Wijnen Request for Comments: 3595 Lucent Technologies Category: Standards Track September 2003 Status of this Memo Textual Conventions for IPv6 Flow Label This document specifies

More information

Category: Standards Track December 1998

Category: Standards Track December 1998 Network Working Group M. Daniele Request for Comments: 2454 Compaq Computer Corporation Category: Standards Track December 1998 Status of this Memo IP Version 6 Management Information Base for the User

More information

Request for Comments: 2493 Category: Standards Track January 1999

Request for Comments: 2493 Category: Standards Track January 1999 Network Working Group K. Tesink, Editor Request for Comments: 2493 Bellcore Category: Standards Track January 1999 Textual Conventions for MIB Modules Using Performance History Based on 15 Minute Intervals

More information

Network Working Group Request for Comments: 3559 Category: Standards Track June 2003

Network Working Group Request for Comments: 3559 Category: Standards Track June 2003 Network Working Group D. Thaler Request for Comments: 3559 Microsoft Category: Standards Track June 2003 Status of this Memo Multicast Address Allocation MIB This document specifies an Internet standards

More information

The Marway Chassis MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.

The Marway Chassis MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions. The Marway Chassis MIB Status of this Memo This document specifies a proprietary MIB module of Marway Power Solutions. Distribution of this memo is limited to Marway product licensees and other interested

More information

Category: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs)

Category: Standards Track September MIB Textual Conventions for Uniform Resource Identifiers (URIs) Network Working Group D. McWalter, Ed. Request for Comments: 5017 Data Connection Ltd Category: Standards Track September 2007 MIB Textual Conventions for Uniform Resource Identifiers (URIs) Status of

More information

Request for Comments: Category: Standards Track S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig May 2002

Request for Comments: Category: Standards Track S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig May 2002 Network Working Group Request for Comments: 3291 Obsoletes: 2851 Category: Standards Track M. Daniele Consultant B. Haberman Consultant S. Routhier Wind River Systems, Inc. J. Schoenwaelder TU Braunschweig

More information

Network Working Group Request for Comments: 4070 Category: Standards Track PESA Switching Systems May 2005

Network Working Group Request for Comments: 4070 Category: Standards Track PESA Switching Systems May 2005 Network Working Group Request for Comments: 4070 Category: Standards Track M. Dodge ECI Telecom B. Ray PESA Switching Systems May 2005 Definitions of Managed Object Extensions for Very High Speed Digital

More information

Network Working Group Request for Comments: K. Rehbehn Megisto Systems, Inc. December 2000

Network Working Group Request for Comments: K. Rehbehn Megisto Systems, Inc. December 2000 Network Working Group Request for Comments: 3020 Category: Standards Track P. Pate B. Lynch Overture Networks K. Rehbehn Megisto Systems, Inc. December 2000 Status of this Memo Definitions of Managed Objects

More information

Network Working Group. Category: Standards Track June Protocol Independent Multicast (PIM) Bootstrap Router MIB

Network Working Group. Category: Standards Track June Protocol Independent Multicast (PIM) Bootstrap Router MIB Network Working Group Request for Comments: 5240 Category: Standards Track B. Joshi Infosys Technologies Ltd. R. Bijlani June 2008 Protocol Independent Multicast (PIM) Bootstrap Router MIB Status of This

More information

The Marway Sensor MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions.

The Marway Sensor MIB. Status of this Memo. This document specifies a proprietary MIB module of Marway Power Solutions. The Marway Sensor MIB Status of this Memo This document specifies a proprietary MIB module of Marway Power Solutions. Distribution of this memo is limited to Marway product licensees and other interested

More information

Request for Comments: 4672 Category: Informational M. Chiba Cisco Systems, Inc. September 2006

Request for Comments: 4672 Category: Informational M. Chiba Cisco Systems, Inc. September 2006 Network Working Group Request for Comments: 4672 Category: Informational S. De Cnodder Alcatel N. Jonnala M. Chiba Cisco Systems, Inc. September 2006 Status of This Memo RADIUS Dynamic Authorization Client

More information

Expires: February 25, 2004 August 27, Using the NETCONF Configuration Protocol over Secure Shell (SSH) draft-wasserman-netconf-over-ssh-00.

Expires: February 25, 2004 August 27, Using the NETCONF Configuration Protocol over Secure Shell (SSH) draft-wasserman-netconf-over-ssh-00. Network Working Group M. Wasserman Internet-Draft Wind River Expires: February 25, 2004 August 27, 2003 Using the NETCONF Configuration Protocol over Secure Shell (SSH) draft-wasserman-netconf-over-ssh-00.txt

More information

Category: Standards Track RAD Data Communications, Ltd. G. Mouradian AT&T Labs October 2000

Category: Standards Track RAD Data Communications, Ltd. G. Mouradian AT&T Labs October 2000 Network Working Group Request for Comments: 2955 Category: Standards Track K. Rehbehn Megisto Systems O. Nicklass RAD Data Communications, Ltd. G. Mouradian AT&T Labs October 2000 Status of this Memo Definitions

More information

Intended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt>

Intended Status: Proposed Standard. Proxy Mobile IPv6 Management Information Base <draft-ietf-netlmm-pmipv6-mib-03.txt> NETLMM Working Group INTERNET-DRAFT Intended Status: Proposed Standard Expires: February 19, 2011 Glenn M. Keeni Cyber Solutions Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota ITC

More information

Network Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999

Network Working Group Request for Comments: 2514 Category: Standards Track Cisco Systems K. Tesink Bellcore Editors February 1999 Network Working Group Request for Comments: 2514 Category: Standards Track M. Noto 3Com E. Spiegel Cisco Systems K. Tesink Bellcore Editors February 1999 Definitions of Textual Conventions and OBJECT-IDENTITIES

More information

draft-aoun-mgcp-nat-package-02.txt

draft-aoun-mgcp-nat-package-02.txt Internet Draft C.Aoun Category Informational M. Wakley T.Sassenberg Nortel Networks Expires on July 28 2003 February 28 2003 A NAT package for MGCP NAT traversal < > Status of this Memo This document is

More information

Network Working Group. Effective Software December 2005

Network Working Group. Effective Software December 2005 Network Working Group Request for Comments: 4318 Category: Standards Track D. Levi Nortel Networks D. Harrington Effective Software December 2005 Status of This Memo Definitions of Managed Objects for

More information

S. Kode Consultant S. Gai Retired September 2006

S. Kode Consultant S. Gai Retired September 2006 Network Working Group Request for Comments: 4625 Category: Standards Track C. DeSanti K. McCloghrie Cisco Systems S. Kode Consultant S. Gai Retired September 2006 Status of This Memo Fibre Channel Routing

More information

Network Working Group. Category: Standards Track Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc.

Network Working Group. Category: Standards Track Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc. Network Working Group Request for Comments: 4295 Category: Standards Track G. Keeni Cyber Solutions Inc. K. Koide Tohoku University K. Nagami INTEC NetCore Inc. S. Gundavelli Cisco Systems Inc. April 2006

More information

Network Working Group. Intended status: Standards Track. January 15, 2010

Network Working Group. Intended status: Standards Track. January 15, 2010 Network Working Group Internet-Draft Intended status: Standards Track Expires: July 19, 2010 G. Zorn Network Zen S. Comerica Cisco Systems January 15, 2010 Diameter Base Protocol MIB draft-ietf-dime-diameter-base-protocol-mib-04.txt

More information

Network Working Group. November Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)

Network Working Group. November Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4) Network Working Group Request for Comments: 3396 Updates: 2131 Category: Standards Track T. Lemon Nominum, Inc. S. Cheshire Apple Computer, Inc. November 2002 Status of this Memo Encoding Long Options

More information

Network Working Group. Obsoletes: draft-ietf-dhc-new-opt-msg-00.txt June 2000 Expires December 2000

Network Working Group. Obsoletes: draft-ietf-dhc-new-opt-msg-00.txt June 2000 Expires December 2000 Network Working Group R. Droms INTERNET-DRAFT Bucknell University Obsoletes: draft-ietf-dhc-new-opt-msg-00.txt June 2000 Expires December 2000 Procedure for Defining New DHCP Options and Message Types

More information

Network Working Group Request for Comments: 4069 Category: Standards Track PESA Switching Systems May 2005

Network Working Group Request for Comments: 4069 Category: Standards Track PESA Switching Systems May 2005 Network Working Group Request for Comments: 4069 Category: Standards Track M. Dodge ECI Telecom B. Ray PESA Switching Systems May 2005 Definitions of Managed Object Extensions for Very High Speed Digital

More information

Expires: October 9, 2005 April 7, 2005

Expires: October 9, 2005 April 7, 2005 DHC B. Volz Internet-Draft Cisco Systems, Inc. Expires: October 9, 2005 April 7, 2005 Status of this Memo DHCPv6 Relay Agent Remote ID Option draft-ietf-dhc-dhcpv6-remoteid-00.txt By submitting this Internet-Draft,

More information

Network Working Group. Category: Standards Track <draft-aboba-radius-iana-03.txt> 30 March 2003 Updates: RFC IANA Considerations for RADIUS

Network Working Group. Category: Standards Track <draft-aboba-radius-iana-03.txt> 30 March 2003 Updates: RFC IANA Considerations for RADIUS Network Working Group INTERNET-DRAFT Category: Standards Track 30 March 2003 Updates: RFC 2865 B. Aboba Microsoft IANA Considerations for RADIUS This document is an Internet-Draft

More information

Internet Engineering Task Force (IETF) Category: Standards Track. J. Quittek. NEC Europe Ltd. October 2012

Internet Engineering Task Force (IETF) Category: Standards Track. J. Quittek. NEC Europe Ltd. October 2012 Internet Engineering Task Force (IETF) Request for Comments: 6727 Category: Standards Track ISSN: 2070-1721 T. Dietz, Ed. NEC Europe Ltd. B. Claise Cisco Systems, Inc. J. Quittek NEC Europe Ltd. October

More information

Request for Comments: 2711 Category: Standards Track BBN October 1999

Request for Comments: 2711 Category: Standards Track BBN October 1999 Network Working Group Request for Comments: 2711 Category: Standards Track C. Partridge BBN A. Jackson BBN October 1999 IPv6 Router Alert Option Status of this Memo This document specifies an Internet

More information

Authentication, Authorization and Accounting Requirements for the Session Initiation Protocol

Authentication, Authorization and Accounting Requirements for the Session Initiation Protocol Internet Engineering Task Force INTERNET-DRAFT draft-ietf-sipping-aaa-req-02.ps SIP WG J. Loughney, G. Camarillo Nokia, Ericsson February 5, 2003 Expires: August, 2003 Authentication, Authorization and

More information

Request for Comments: 1901

Request for Comments: 1901 Network Working Group Request for Comments: 1901 Category: Experimental SNMPv2 Working Group J. Case SNMP Research, Inc. K. McCloghrie Cisco Systems, Inc. M. Rose Dover Beach Consulting, Inc. S. Waldbusser

More information

E. Lewis ARIN September 23, KEY RR Secure Entry Point Flag draft-ietf-dnsext-keyrr-key-signing-flag-09. Status of this Memo

E. Lewis ARIN September 23, KEY RR Secure Entry Point Flag draft-ietf-dnsext-keyrr-key-signing-flag-09. Status of this Memo DNS Extensions Internet-Draft Expires: March 23, 2004 O. Kolkman RIPE NCC J. Schlyter E. Lewis ARIN September 23, 2003 Status of this Memo KEY RR Secure Entry Point Flag draft-ietf-dnsext-keyrr-key-signing-flag-09

More information

Request for Comments: 5488 Category: Standards Track Cyber Solutions K. Koide KDDI CORPORATION K. Nagami INTEC NetCore April 2009

Request for Comments: 5488 Category: Standards Track Cyber Solutions K. Koide KDDI CORPORATION K. Nagami INTEC NetCore April 2009 Network Working Group Request for Comments: 5488 Category: Standards Track S. Gundavelli Cisco G. Keeni Cyber Solutions K. Koide KDDI CORPORATION K. Nagami INTEC NetCore April 2009 Status of This Memo

More information

Request for Comments: 5488 Category: Standards Track. Network Mobility (NEMO) Management Information Base

Request for Comments: 5488 Category: Standards Track. Network Mobility (NEMO) Management Information Base V W I D E P R O J E C T 5 1 Introduction 2 NEMO-MIB: A MIB module for Network Mobility 5 The WIDE-Netman-Working-Group has been carrying out research and development to make the Internet more manageable

More information

Category: Informational 1 April Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2

Category: Informational 1 April Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using SMIv2 Network Working Group M. Slavitch Request for Comments: 2325 Loran Technologies Inc. Category: Informational 1 April 1998 Definitions of Managed Objects for Drip-Type Heated Beverage Hardware Devices using

More information

Network Working Group. Intended status: Standards Track Columbia U. Expires: March 5, 2009 September 1, 2008

Network Working Group. Intended status: Standards Track Columbia U. Expires: March 5, 2009 September 1, 2008 Network Working Group O. Boyaci Internet-Draft H. Schulzrinne Intended status: Standards Track Columbia U. Expires: March 5, 2009 September 1, 2008 RTP Payload Format for Portable Network Graphics (PNG)

More information

Network Working Group. Category: Informational January Unused Dynamic Host Configuration Protocol (DHCP) Option Codes

Network Working Group. Category: Informational January Unused Dynamic Host Configuration Protocol (DHCP) Option Codes Network Working Group R. Droms Request for Comments: 3679 Cisco Systems Category: Informational January 2004 Unused Dynamic Host Configuration Protocol (DHCP) Option Codes Status of this Memo This memo

More information

RADIUS Working Group Bernard Aboba. Category: Standards Track <draft-ietf-radius-auth-clientmib-01.txt> 12 February 1998

RADIUS Working Group Bernard Aboba. Category: Standards Track <draft-ietf-radius-auth-clientmib-01.txt> 12 February 1998 RADIUS Working Group Bernard Aboba INTERNET-DRAFT Microsoft Category: Standards Track Glen Zorn Microsoft 12 February 1998 RADIUS Authentication Client MIB 1.

More information

Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E)

Definitions of Managed Objects for Mapping of Address and Port with Encapsulation (MAP-E) Internet Engineering Task Force (IETF) Request for Comments: 8389 Category: Standards Track ISSN: 2070-1721 Y. Fu CNNIC S. Jiang B. Liu Huawei Technologies Co., Ltd J. Dong Y. Chen Tsinghua University

More information

Internet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012

Internet Engineering Task Force (IETF) Category: Standards Track. S. Gundavelli Cisco R. Wakikawa Toyota ITC May 2012 Internet Engineering Task Force (IETF) Request for Comments: 6475 Category: Standards Track ISSN: 2070-1721 G. Keeni Cyber Solutions, Inc. K. Koide KDDI Corporation S. Gundavelli Cisco R. Wakikawa Toyota

More information

draft-ietf-sip-info-method-02.txt February 2000 The SIP INFO Method Status of this Memo

draft-ietf-sip-info-method-02.txt February 2000 The SIP INFO Method Status of this Memo HTTP/1.1 200 OK Date: Tue, 09 Apr 2002 07:53:57 GMT Server: Apache/1.3.20 (Unix) Last-Modified: Tue, 15 Feb 2000 17:03:00 GMT ETag: "3239a5-465b-38a986c4" Accept-Ranges: bytes Content-Length: 18011 Connection:

More information

Category: Standards Track September 2003

Category: Standards Track September 2003 Network Working Group K. Murchison Request for Comments: 3598 Oceana Matrix Ltd. Category: Standards Track September 2003 Status of this Memo Sieve Email Filtering -- Subaddress Extension This document

More information

Internet Engineering Task Force (IETF) Category: Standards Track. K. Patel Cisco Systems M. Baer SPARTA May 2013

Internet Engineering Task Force (IETF) Category: Standards Track. K. Patel Cisco Systems M. Baer SPARTA May 2013 Internet Engineering Task Force (IETF) Request for Comments: 6945 Category: Standards Track ISSN: 2070-1721 R. Bush Internet Initiative Japan B. Wijnen RIPE NCC K. Patel Cisco Systems M. Baer SPARTA May

More information

Expires in six months 24 October 2004 Obsoletes: RFC , , 3377, 3771

Expires in six months 24 October 2004 Obsoletes: RFC , , 3377, 3771 INTERNET-DRAFT Editor: Kurt D. Zeilenga Intended Category: Standard Track OpenLDAP Foundation Expires in six months 24 October 2004 Obsoletes: RFC 2251-2256, 2829-2830, 3377, 3771 Lightweight Directory

More information

Request for Comments: Oversi O. Nicklass, Ed. RADVISION May Definitions of Textual Conventions for Pseudowire (PW) Management

Request for Comments: Oversi O. Nicklass, Ed. RADVISION May Definitions of Textual Conventions for Pseudowire (PW) Management Network Working Group Request for Comments: 5542 Category: Standards Track T. Nadeau, Ed. BT D. Zelig, Ed. Oversi O. Nicklass, Ed. RADVISION May 2009 Definitions of Textual Conventions for Pseudowire (PW)

More information

Network Working Group Request for Comments: 3634 Category: Standards Track Comcast Cable J. Bevilacqua N. Davoust YAS Corporation December 2003

Network Working Group Request for Comments: 3634 Category: Standards Track Comcast Cable J. Bevilacqua N. Davoust YAS Corporation December 2003 Network Working Group Request for Comments: 3634 Category: Standards Track K. Luehrs CableLabs R. Woundy Comcast Cable J. Bevilacqua N. Davoust YAS Corporation December 2003 Key Distribution Center (KDC)

More information

Network Working Group. January 2008

Network Working Group. January 2008 Network Working Group Request for Comments: 5097 Category: Standards Track G. Renker G. Fairhurst University of Aberdeen January 2008 MIB for the UDP-Lite Protocol Status of This Memo This document specifies

More information

Network Working Group Request for Comments: December 1998

Network Working Group Request for Comments: December 1998 Network Working Group Request for Comments: 2466 Category: Standards Track D. Haskin S. Onishi Bay Networks, Inc. December 1998 Status of this Memo Management Information Base for IP Version 6: ICMPv6

More information

Category: Standards Track December 2003

Category: Standards Track December 2003 Network Working Group R. Droms, Ed. Request for Comments: 3646 Cisco Systems Category: Standards Track December 2003 Status of this Memo DNS Configuration options for Dynamic Host Configuration Protocol

More information

XDI Requirements and Use Cases

XDI Requirements and Use Cases 1 2 3 XDI Requirements and Use Cases Working Draft 01, April 19 th 2004 4 5 6 7 8 9 10 11 12 13 14 Document identifier: xdi-requirements-and-use-cases-document-04 Location: Editors: [Editors listed here]

More information

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-00.

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-00. Network Working Group J. Snell Internet-Draft August 2005 Expires: February 2, 2006 Status of this Memo Atom Link No Follow draft-snell-atompub-feed-nofollow-00.txt By submitting this Internet-Draft, each

More information

Category: Standards Track July 2002

Category: Standards Track July 2002 Network Working Group A. Bierman Request for Comments: 3287 Cisco Systems, Inc. Category: Standards Track July 2002 Status of this Memo Remote Monitoring MIB Extensions for Differentiated Services This

More information

Internet Engineering Task Force (IETF) Request for Comments: 7330 Category: Standards Track. Cisco Systems August 2014

Internet Engineering Task Force (IETF) Request for Comments: 7330 Category: Standards Track. Cisco Systems August 2014 Internet Engineering Task Force (IETF) Request for Comments: 7330 Category: Standards Track ISSN: 2070-1721 T. Nadeau Brocade Z. Ali N. Akiya Cisco Systems August 2014 Definitions of Textual Conventions

More information

Network Working Group Internet-Draft January 25, 2006 Expires: July 29, Feed Rank draft-snell-atompub-feed-index-05.txt. Status of this Memo

Network Working Group Internet-Draft January 25, 2006 Expires: July 29, Feed Rank draft-snell-atompub-feed-index-05.txt. Status of this Memo Network Working Group J. Snell Internet-Draft January 25, 2006 Expires: July 29, 2006 Status of this Memo Feed Rank draft-snell-atompub-feed-index-05.txt By submitting this Internet-Draft, each author

More information

Softwire Mesh Management Information Base (MIB)

Softwire Mesh Management Information Base (MIB) Internet Engineering Task Force (IETF) Request for Comments: 7856 Category: Standards Track ISSN: 2070-1721 Y. Cui J. Dong P. Wu M. Xu Tsinghua University A. Yla-Jaaski Aalto University May 2016 Softwire

More information

Network Working Group Request for Comments: Category: Best Current Practice January 2004

Network Working Group Request for Comments: Category: Best Current Practice January 2004 Network Working Group R. Bush Request for Comments: 3681 IIJ BCP: 80 R. Fink Category: Best Current Practice January 2004 Status of this Memo Delegation of E.F.F.3.IP6.ARPA This document specifies an Internet

More information

Network Working Group. Category: Standards Track February SIEVE Filtering: Spamtest and VirusTest Extensions

Network Working Group. Category: Standards Track February SIEVE  Filtering: Spamtest and VirusTest Extensions Network Working Group C. Daboo Request for Comments: 3685 Cyrusoft International, Inc. Category: Standards Track February 2004 SIEVE Email Filtering: Spamtest and VirusTest Extensions Status of this Memo

More information

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-03.

Network Working Group Internet-Draft August 2005 Expires: February 2, Atom Link No Follow draft-snell-atompub-feed-nofollow-03. Network Working Group J. Snell Internet-Draft August 2005 Expires: February 2, 2006 Status of this Memo Atom Link No Follow draft-snell-atompub-feed-nofollow-03.txt By submitting this Internet-Draft, each

More information

Request for Comments: Cisco Systems, Inc. M. Rose Dover Beach Consulting, Inc. S. Waldbusser International Network Services January 1996

Request for Comments: Cisco Systems, Inc. M. Rose Dover Beach Consulting, Inc. S. Waldbusser International Network Services January 1996 Network Working Group Request for Comments: 1908 Obsoletes: 1452 Category: Standards Track SNMPv2 Working Group J. Case SNMP Research, Inc. K. McCloghrie Cisco Systems, Inc. M. Rose Dover Beach Consulting,

More information

Network Working Group. Category: Standards Track Cisco Systems, Inc. April 2004

Network Working Group. Category: Standards Track Cisco Systems, Inc. April 2004 Network Working Group Request for Comments: 3737 Category: Standards Track B. Wijnen Lucent Technologies A. Bierman Cisco Systems, Inc. April 2004 Status of this Memo IANA Guidelines for the Registry of

More information

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: October 2015

Internet Engineering Task Force (IETF) Category: Standards Track ISSN: October 2015 Internet Engineering Task Force (IETF) Request for Comments: 7630 Category: Standards Track ISSN: 2070-1721 J. Merkle, Ed. Secunet Security Networks M. Lochter BSI October 2015 HMAC-SHA-2 Authentication

More information

Network Working Group Internet-Draft October 27, 2007 Intended status: Experimental Expires: April 29, 2008

Network Working Group Internet-Draft October 27, 2007 Intended status: Experimental Expires: April 29, 2008 Network Working Group J. Snell Internet-Draft October 27, 2007 Intended status: Experimental Expires: April 29, 2008 Status of this Memo Atom Publishing Protocol Feature Discovery draft-snell-atompub-feature-12.txt

More information

Internet Engineering Task Force (IETF) Updates: 5066 February 2014 Category: Standards Track ISSN:

Internet Engineering Task Force (IETF) Updates: 5066 February 2014 Category: Standards Track ISSN: Internet Engineering Task Force (IETF) E. Beili Request for Comments: 7124 Actelis Networks Updates: 5066 February 2014 Category: Standards Track ISSN: 2070-1721 Abstract Ethernet in the First Mile Copper

More information

Request for Comments: Cisco Systems S. Gai Retired September MIB for Fibre Channel s Fabric Shortest Path First (FSPF) Protocol

Request for Comments: Cisco Systems S. Gai Retired September MIB for Fibre Channel s Fabric Shortest Path First (FSPF) Protocol Network Working Group Request for Comments: 4626 Category: Standards Track C. DeSanti V. Gaonkar K. McCloghrie Cisco Systems S. Gai Retired September 2006 MIB for Fibre Channel s Fabric Shortest Path First

More information

Innosoft January 1994

Innosoft January 1994 Network Working Group Request for Comments: 1566 Category: Standards Track S. Kille, WG Chair ISODE Consortium N. Freed, Editor Innosoft January 1994 Mail Monitoring MIB Status of this Memo This document

More information

Network Working Group Request for Comments: 3397 Category: Standards Track Apple Computer, Inc. November 2002

Network Working Group Request for Comments: 3397 Category: Standards Track Apple Computer, Inc. November 2002 Network Working Group Request for Comments: 3397 Category: Standards Track B. Aboba Microsoft S. Cheshire Apple Computer, Inc. November 2002 Dynamic Host Configuration Protocol (DHCP) Domain Search Option

More information

Updates: 2710 September 2003 Category: Standards Track. Source Address Selection for the Multicast Listener Discovery (MLD) Protocol

Updates: 2710 September 2003 Category: Standards Track. Source Address Selection for the Multicast Listener Discovery (MLD) Protocol Network Working Group B. Haberman Request for Comments: 3590 Caspian Networks Updates: 2710 September 2003 Category: Standards Track Status of this Memo Source Address Selection for the Multicast Listener

More information

Internet Engineering Task Force. Intended status: Standards Track. May 3, 2009

Internet Engineering Task Force. Intended status: Standards Track. May 3, 2009 Page 1 of 46 Internet Engineering Task Force Internet-Draft Intended status: Standards Track Expires: November 4, 2009 R. Cole Johns Hopkins University T. Clausen LIX, Ecole Polytechnique May 3, 2009 Definition

More information

Obsoletes: 4369 March 2011 Category: Standards Track ISSN: Definitions of Managed Objects for the Internet Fibre Channel Protocol (ifcp)

Obsoletes: 4369 March 2011 Category: Standards Track ISSN: Definitions of Managed Objects for the Internet Fibre Channel Protocol (ifcp) Internet Engineering Task Force (IETF) P. Venkatesen, Ed. Request for Comments: 6173 HCL Technologies Obsoletes: 4369 March 2011 Category: Standards Track ISSN: 2070-1721 Abstract Definitions of Managed

More information

Jabber, Inc. August 20, 2004

Jabber, Inc. August 20, 2004 Network Working Group Internet-Draft Expires: February 18, 2005 P. Saint-Andre Jabber Software Foundation J. Hildebrand Jabber, Inc. August 20, 2004 Transporting Atom Notifications over the Extensible

More information

Category: Standards Track December 2007

Category: Standards Track December 2007 Network Working Group V. Devarapalli Request for Comments: 5096 Azaire Networks Category: Standards Track December 2007 Status of This Memo Mobile IPv6 Experimental Messages This document specifies an

More information

Internet Engineering Task Force (IETF) Request for Comments: C. Zhou Huawei Technologies October 2014

Internet Engineering Task Force (IETF) Request for Comments: C. Zhou Huawei Technologies October 2014 Internet Engineering Task Force (IETF) Request for Comments: 7388 Category: Standards Track ISSN: 2070-1721 J. Schoenwaelder A. Sehgal Jacobs University T. Tsou C. Zhou Huawei Technologies October 2014

More information

Internet Engineering Task Force (IETF) B. Claise Cisco Systems, Inc. G. Muenz Technische Universitaet Muenchen April 2010

Internet Engineering Task Force (IETF) B. Claise Cisco Systems, Inc. G. Muenz Technische Universitaet Muenchen April 2010 Internet Engineering Task Force (IETF) Request for Comments: 5815 Category: Standards Track ISSN: 2070-1721 T. Dietz, Ed. NEC Europe, Ltd. A. Kobayashi NTT PF Labs. B. Claise Cisco Systems, Inc. G. Muenz

More information

Category: Standards Track Cisco Systems A. Karmakar Cisco Systems India Pvt Ltd October 2009

Category: Standards Track Cisco Systems A. Karmakar Cisco Systems India Pvt Ltd October 2009 Network Working Group Request for Comments: 5676 Category: Standards Track J. Schoenwaelder Jacobs University Bremen A. Clemm Cisco Systems A. Karmakar Cisco Systems India Pvt Ltd October 2009 Abstract

More information

Network Working Group Request for Comments: December 2004

Network Working Group Request for Comments: December 2004 Network Working Group Request for Comments: 3967 BCP: 97 Category: Best Current Practice R. Bush IIJ T. Narten IBM Corporation December 2004 Status of this Memo Clarifying when Standards Track Documents

More information

Using SRP for TLS Authentication

Using SRP for TLS Authentication Using SRP for TLS Authentication Internet Draft Transport Layer Security Working Group D. Taylor Forge Research Pty Ltd Expires: March 5, 2003 September 4, 2002 Using SRP for TLS Authentication draft-ietf-tls-srp-03

More information

Use and Interpretation of HTTP Version Numbers

Use and Interpretation of HTTP Version Numbers Network Working Group Request for Comments: 2145 Category: Informational J. Mogul DEC R. Fielding UC Irvine J. Gettys DEC H. Frystyk MIT/LCS May 1997 Use and Interpretation of HTTP Version Numbers Status

More information

Updates: 2535 November 2003 Category: Standards Track

Updates: 2535 November 2003 Category: Standards Track Network Working Group B. Wellington Request for Comments: 3655 O. Gudmundsson Updates: 2535 November 2003 Category: Standards Track Status of this Memo Redefinition of DNS Authenticated Data (AD) bit This

More information

Request for Comments: Accton Technology Corporation February Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP)

Request for Comments: Accton Technology Corporation February Definitions of Managed Objects for Fibre Channel Over TCP/IP (FCIP) Network Working Group Request for Comments: 4404 Category: Standards Track R. Natarajan F5 Networks A. Rijhsinghani Accton Technology Corporation February 2006 Definitions of Managed Objects for Fibre

More information

Category: Standards Track October 2006

Category: Standards Track October 2006 Network Working Group C. Perkins Request for Comments: 4636 Nokia Research Center Category: Standards Track October 2006 Status of This Memo Foreign Agent Error Extension for Mobile IPv4 This document

More information

Deployment Profile Template Version 1.0 for WS-Reliability 1.1

Deployment Profile Template Version 1.0 for WS-Reliability 1.1 Deployment Profile Template Version 1.0 for WS-Reliability 1.1 Committee Draft 11 April 2007 URIs: This Version: http://docs.oasis-open.org/wsrm/profile/wsr-deployment-profile-template-cd.pdf Latest Version:

More information

Network Working Group. Category: Standards Track June Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option

Network Working Group. Category: Standards Track June Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option Network Working Group B. Volz Request for Comments: 4580 Cisco Systems, Inc. Category: Standards Track June 2006 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Subscriber-ID Option Status

More information

Request for Comments: 5010 Category: Standards Track Cisco Systems, Inc. September 2007

Request for Comments: 5010 Category: Standards Track Cisco Systems, Inc. September 2007 Network Working Group Request for Comments: 5010 Category: Standards Track K. Kinnear M. Normoyle M. Stapp Cisco Systems, Inc. September 2007 The Dynamic Host Configuration Protocol Version 4 (DHCPv4)

More information

Network Working Group. Category: Standards Track August Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option

Network Working Group. Category: Standards Track August Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option Network Working Group B. Volz Request for Comments: 4649 Cisco Systems, Inc. Category: Standards Track August 2006 Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option Status

More information

Request for Comments: 3934 Updates: 2418 October 2004 BCP: 94 Category: Best Current Practice

Request for Comments: 3934 Updates: 2418 October 2004 BCP: 94 Category: Best Current Practice Network Working Group M. Wasserman Request for Comments: 3934 ThingMagic Updates: 2418 October 2004 BCP: 94 Category: Best Current Practice Updates to RFC 2418 Regarding the Management of IETF Mailing

More information

Network Working Group. Category: Informational May OSPF Database Exchange Summary List Optimization

Network Working Group. Category: Informational May OSPF Database Exchange Summary List Optimization Network Working Group R. Ogier Request for Comments: 5243 SRI International Category: Informational May 2008 Status of This Memo OSPF Database Summary List Optimization This memo provides information for

More information

Internet Engineering Task Force (IETF) Category: Standards Track. December 2018

Internet Engineering Task Force (IETF) Category: Standards Track. December 2018 Internet Engineering Task Force (IETF) Request for Comments: 8502 Category: Standards Track ISSN: 2070-1721 Z. Zhang Juniper Networks, Inc. H. Tsunoda Tohoku Institute of Technology December 2018 L2L3

More information

Internet Engineering Task Force (IETF) Request for Comments: 5907 Category: Standards Track ISSN: B. Haberman, Ed.

Internet Engineering Task Force (IETF) Request for Comments: 5907 Category: Standards Track ISSN: B. Haberman, Ed. Internet Engineering Task Force (IETF) Request for Comments: 5907 Category: Standards Track ISSN: 2070-1721 H. Gerstung Meinberg C. Elliott B. Haberman, Ed. JHU APL June 2010 Definitions of Managed Objects

More information

Category: Standards Track October Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4)

Category: Standards Track October Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version 4 (DHCPv4) Network Working Group J. Littlefield Request for Comments: 3925 Cisco Systems, Inc. Category: Standards Track October 2004 Vendor-Identifying Vendor Options for Dynamic Host Configuration Protocol version

More information

Category: Standards Track Cisco Systems, Inc. March 2005

Category: Standards Track Cisco Systems, Inc. March 2005 Network Working Group Request for Comments: 3993 Category: Standards Track R. Johnson T. Palaniappan M. Stapp March 2005 Subscriber-ID Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay

More information

Network Working Group. Category: Standards Track Nortel Networks S. Routhier Integrated Systems Inc. B. Wijnen Lucent Technologies March 2000

Network Working Group. Category: Standards Track Nortel Networks S. Routhier Integrated Systems Inc. B. Wijnen Lucent Technologies March 2000 Network Working Group Request for Comments: 2576 Category: Standards Track R. Frye CoSine Communications D. Levi Nortel Networks S. Routhier Integrated Systems Inc. B. Wijnen Lucent Technologies March

More information

Intended status: Standards Track Expires: April 27, 2015 Q. Zhao Huawei Technology D. King Old Dog Consulting J. Hardwick Metaswitch October 24, 2014

Intended status: Standards Track Expires: April 27, 2015 Q. Zhao Huawei Technology D. King Old Dog Consulting J. Hardwick Metaswitch October 24, 2014 PCE Working Group Internet-Draft Intended status: Standards Track Expires: April 27, 2015 A. Koushik Brocade Communications Inc. E. Stephan Orange Q. Zhao Huawei Technology D. King Old Dog Consulting J.

More information

SSTC Response to Security Analysis of the SAML Single Sign-on Browser/Artifact Profile

SSTC Response to Security Analysis of the SAML Single Sign-on Browser/Artifact Profile 1 2 3 4 5 SSTC Response to Security Analysis of the SAML Single Sign-on Browser/Artifact Profile Working Draft 01, 24 January 2005 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

More information

Network Working Group Request for Comments: 3937 Category: Informational October 2004

Network Working Group Request for Comments: 3937 Category: Informational October 2004 Network Working Group M. Steidl Request for Comments: 3937 IPTC Category: Informational October 2004 A Uniform Resource Name (URN) Namespace for the International Press Telecommunications Council (IPTC)

More information