« Prev | Issue 490 — 2007-11-02
2007-11-02
Data differences from 2007-11-01 06:00:40 to 2007-11-02 06:00:42
IETF-Announce List
- Internet-Drafts Submission Cutoff Dates for the 70th IETF Meeting in Vancouver, BC, Canada (ietf-secretariat)
- WG Action: Conclusion of IP Storage WG (ips) (IESG Secretary)
- Last Call: draft-ietf-avt-rfc3119bis (A More Loss-Tolerant RTP Payload Format for MP3 Audio) to Proposed Standard (The IESG)
New RFCs
New and Revived Drafts
- draft-auerbach-mgcp-rtcpxr
"RTCP XR VoIP Metrics Package for the Media Gateway Control Protocol", David Auerbach, 1-Nov-07 TXT HTML PDF
Abstract: The main intent of this document is to define a Media Gateway Control Protocol (MGCP) package to control the reporting of metrics supported by the VoIP metrics block in RTCP Extended Reports as specified in [RFC 3611]. It also allows the call agent to control whether or not the gateway will request a peer device via SDP to send the VoIP metrics block in RTCP Extended Reports and whether it will respond positively to such requests from the peer device. Besides this primary focus, this MGCP RTCP-XR Package 4/12/2007 package also allows the reporting of metrics defined for RTCP Sender Reports and Receiver Reports [RFC 3550] and the reporting of session description parameters (based on the ones defined in RFC 2327, RFC 2198 etc.).
- draft-hallambaker-ocspagility
- draft-li-ccamp-wson-igp-eval
"Evaluation of Possible Interior Gateway Protocol Extensions for Wavelength Switching Optical Networks", Dan Li, 1-Nov-07 TXT HTML PDF
Abstract: Wavelength Division Multiplexing (WDM) is a technology for optical communications, in which the user traffic is carried by data channels of different optical wavelengths. In traditional WDM Networks, each wavelength path is statically configured. With the deployment of the Reconfigurable Optical Add-Drop Multiplexer (ROADM) and the Wavelength Selective Switch (WSS), WDM networks have become more dynamic, and operators can flexibly set up wavelength paths to carry user traffic. This document discusses the set of Interior Gateway Protocol (IGP) requirements that would enable distributed light path computation in Wavelength Switched Optical Networks (WSON). An IGP impact analysis is also provided. According to the analysis, there is no significant impact on the IGP performance.
- draft-mun-mipshop-emipv6-aaa
"An Enhanced Mobile IPv6 Handover for Roaming between Administrative Domains Based on AAA", Youngsong Mun, 1-Nov-07 TXT HTML PDF
Abstract: When Mobile IPv6 (MIPv6) is deployed in commercial network, a mobile node needs AAA services for authentication, authorization and accounting. MIPv6, however, does not provide any mean to authenticate mobile nodes that are roaming in different domains, although visited networks will need to check whether access of mobile nodes should be authorized or not. Hence schemes which support both AAA services and mobility have been emerged. These schemes enable access of the mobile node to be authorized by visited networks through AAA as well as to perform a home registration during AAA procedure. However, they introduce lots of signal messages and long handover latency during handover, since Route Optimization mode for MIPv6 is performed using Return Routability procedure. Especially, the long handover latency is a critical problem in real-time communication such as voice over IP (VoIP). To solve these problems, we propose an optimized scheme which performs Route Optimization mode using the AAA infrastructure between the home agent and a correspondent node instead of Return Routability procedure.
- draft-tewari-federated-fs-protocol
"Protocol for Federated Filesystems v1.0", Renu Tewari, Manoj Naik, Daniel Ellard, Craig Everhart, 1-Nov-07 TXT HTML PDF
Abstract: This document describes a file system federation protocol that enables file access and namespace traversal across collections of independently administered fileservers. The protocol specifies a set of interfaces by which fileservers and collections of fileservers with different administrators can form a fileserver federation that provides a namespace composed of the filesystems physically hosted on and exported by the constituent fileservers. RFC 2119 Keywords The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119
Updated Drafts
- draft-berger-l3vpn-ip-tunnels
"BGP/IP VPNs: BGP Support for IPv4 and IPv6 Tunneled Layer Three Virtual Private Networks (VPNs)", Lou Berger, Ronald Bonica, Russ White, Intellectual Property, 24-Oct-07 TXT HTML PDF
Abstract: The basic principles for the control of IP Virtual Private Networks (VPNs) using Border Gateway Protocol (BGP) is defined in BGP/MPLS IP VPNs for both IPv4 and IPv6. These definitions are limited to networks and routers that support Multiprotocol Label Switching (MPLS). This document extends BGP based control of IP VPNs to any IP VPN technology that use tunnels that are identified based on IP addresses rather than MPLS labels. Examples of IP tunnel technology include IP-in-IP, GRE, and IPsec tunnels. Support for IPv4 and IPv6 VPNs and tunnels are defined. It is expected that the extensions defined in this document will be most useful in environments where it is not possible to use MPLS, such as in customer provided VPNs.Contents
- draft-gaonkar-radext-erp-attrs
"RADIUS Support for EAP Re-authentication Protocol", Kedar Gaonkar, Lakshminath Dondeti, Vidya Narayanan, Glen Zorn, 1-Nov-07 TXT HTML PDF
Abstract: RFCxxxx (draft-ietf-hokey-erx after publication) [6] specifies the EAP Re-authentication Protocol (ERP). This document specifies RADIUS support for ERP. The procedures in RFC3579 [1] are used for encapsulating the EAP Initiate and Finish messages specified in RFCxxxx (draft-ietf-hokey-erx after publication) [6]. This document specifies attributes for the request and delivery of Domain Specific Root Keys from the AAA/EAP server to the ER Server. Additionally, this document also specifies RADIUS message processing rules relevant to ERP.
- draft-ietf-nea-requirements
"Network Endpoint Assessment (NEA): Overview and Requirements", Paul Sangster, 1-Nov-07 TXT HTML PDF
Abstract: This document defines the problem statement, scope and protocol requirements between the components of the NEA (Network Endpoint Assessment) reference model. NEA provides owners of networks (e.g. an enterprise offering remote access) a mechanism to evaluate the posture of a system. This may take place during the request for network access and/or subsequently at any time while connected to the network. The learned posture information can then be applied to a variety of compliance oriented decisions. The posture information is frequently useful for detecting systems that are lacking or have out of date security protective mechanisms such as: anti-virus and host-based firewall software. In order to provide context for the requirements, a reference model and terminology are introduced.
- draft-ietf-pce-policy-enabled-path-comp
"Policy-Enabled Path Computation Framework", Igor Bryskin, Dimitri Papadimitriou, Lou Berger, Gerald Ash, Intellectual Property, 1-Nov-07 TXT HTML PDF
Abstract: The Path Computation Element (PCE) Architecture introduces the concept of policy in the context of path computation. This document provides additional details on policy within the PCE Architecture and also provides context for the support of PCE Policy. This document introduces the use of the Policy Core Information Model (PCIM) as a framework for supporting path computation policy. This document also provides representative scenarios for the support of PCE Policy.Contents
- draft-ietf-shim6-proto
"Shim6: Level 3 Multihoming Shim Protocol for IPv6", Marcelo Bagnulo, Erik Nordmark, 1-Nov-07 TXT HTML PDF
Abstract: This document defines the Shim6 protocol, a layer 3 shim for providing locator agility below the transport protocols, so that multihoming can be provided for IPv6 with failover and load sharing properties, without assuming that a multihomed site will have a provider independent IPv6 address prefix which is announced in the global IPv6 routing table. The hosts in a site which has multiple provider allocated IPv6 address prefixes, will use the Shim6 protocol specified in this document to setup state with peer hosts, so that the state can later be used to failover to a different locator pair, should the original one stop working.
Diff from 08 to 09 »
State: AD Evaluation::AD Followup
ID Tracker » ATOM
Document details »
SHIM6 WG »
- draft-wilde-text-fragment
"URI Fragment Identifiers for the text/plain Media Type", Erik Wilde, Martin Duerst, 1-Nov-07 TXT HTML PDF
Abstract: This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust.
Diff from 08 to 09 »
State: IESG Evaluation::AD Followup
ID Tracker » ATOM
Expired Drafts
- draft-ietf-adslmib-gbond-tdim-mib
- draft-ietf-isis-hmac-sha
- draft-irtf-tmrg-ns2-tcp-tool
- draft-xia-netlmm-service-negotiation
Drafts Sent to IESG
- draft-ietf-mip4-nemo-v4-base
"Network Mobility (NEMO) Extensions for Mobile IPv4", Kent Leung, Gopal Dommety, Vidya Narayanan, Alexandru Petrescu, 31-Oct-07 TXT HTML PDF
Abstract: This document describes a protocol for supporting Mobile Networks between a Mobile Router and a Home Agent by extending the Mobile IPv4 protocol. A Mobile Router is responsible for the mobility of one or more network segments or subnets moving together. The Mobile Router hides its mobility from the nodes on the mobile network. The nodes on the Mobile Network may be fixed in relationship to the Mobile Router and may not have any mobility function. Extensions to Mobile IPv4 are introduced to support Mobile Networks.
State: Publication Requested
ID Tracker » ATOM
Document details »
MIP4 WG »
- draft-ietf-pim-lasthop-threats
"Host Threats to Protocol Independent Multicast (PIM)", Pekka Savola, James Lingard, 10-Oct-07 TXT HTML PDF
Abstract: This memo complements the list of multicast infrastructure security threat analysis documents by describing Protocol Independent Multicast (PIM) threats specific to router interfaces connecting hosts.
State: Publication Requested
ID Tracker » ATOM
Document details »
PIM WG »
IESG Progress
- draft-ietf-avt-avpf-ccm : IESG Evaluation » Approved-announcement to be sent
"Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)", Stephan Wenger, Umesh Chandra, Magnus Westerlund, Bo Burman, 26-Oct-07 TXT HTML PDF
Abstract: This document specifies a few extensions to the messages defined in the Audio-Visual Profile with Feedback (AVPF). They are helpful primarily in conversational multimedia scenarios where centralized multipoint functionalities are in use. However, some are also usable in smaller multicast environments and point-to-point calls. The extensions discussed are messages related to the ITU-T H.271 Video Back Channel, Full Intra Request, Temporary Maximum Media Stream Bit Rate and Temporal Spatial Trade-off.
State: Approved-announcement to be sent
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-rfc3119bis : AD Evaluation » In Last Call
"A More Loss-Tolerant RTP Payload Format for MP3 Audio", Ross Finlayson, 29-Aug-07 TXT HTML PDF
Abstract: This document describes a RTP (Real-Time Protocol) payload format for transporting MPEG (Moving Picture Experts Group) 1 or 2, layer III audio (commonly known as "MP3"). This format is an alternative to that described in RFC 2250, and performs better if there is packet loss. (This document updates (and obsoletes) RFC 3119, correcting typographical errors in the "SDP usage" section and pseudo-code appendices.)
State: In Last Call
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-rtp-evrc-wb : IESG Evaluation » IESG Evaluation::Revised ID Needed
"RTP payload format for EVRC-WB codec and media subtype updates for EVRC-B codec", HariKishan Desineni, Dae Young Kim, 1-Nov-07 TXT HTML PDF
Abstract: This document specifies real-time transport protocol (RTP) payload formats to be used for the EVRC wideband codec (EVRC-WB) and updates the media type registrations for EVRC-B codec. Several media type registrations are included for EVRC-WB RTP payload formats. In addition, a file format is specified for transport of EVRC-WB speech data in storage mode applications such as e-mail.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-rtp-jpeg2000 : AD Evaluation » AD Evaluation::External Party
"RTP Payload Format for JPEG 2000 Video Streams", Satoshi Futemma, 12-Sep-07 TXT HTML PDF
Abstract: This memo describes an RTP payload format for the ISO/IEC International Standard 15444-1 | ITU-T Rec. T.800, otherwise better known as: JPEG 2000. JPEG 2000 features are considered in the design of this payload format. JPEG 2000 is a truly scalable compression technology allowing applications to encode once and decode many different ways. JPEG 2000 video stream is formed by extending from a single image to a series of JPEG 2000 images.
State: AD Evaluation::External Party
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-rtp-jpeg2000-beam : AD Evaluation » AD Evaluation::External Party
"Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header Recovery", Andrew Leung, 12-Sep-07 TXT HTML PDF
Abstract: This memo describes extended uses for payload header in RFC document: "RTP Payload Format for JPEG 2000 Video Streams." For better support of JPEG 2000 features such as scalability and includes a main header recovery method. This memo must be accompanied with a complete implementation of "RTP Payload Format for JPEG 2000 Video Streams." That document is a complete description of the payload header and signaling, this document only describes additional processing for the payload header. There is an additional media type and SDP marker signaling for implementations of this document.
State: AD Evaluation::External Party
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-rtp-vorbis : IESG Evaluation » IESG Evaluation::Revised ID Needed
"RTP Payload Format for Vorbis Encoded Audio", Luca Barbato, 23-Aug-07 TXT HTML PDF
Abstract: This document describes an RTP payload format for transporting Vorbis encoded audio. It details the RTP encapsulation mechanism for raw Vorbis data and details the delivery mechanisms for the decoder probability model, referred to as a codebook and other setup information. Also included within this memo are media type registrations, and the details necessary for the use of Vorbis with the Session Description Protocol (SDP).
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-avt-topologies : IESG Evaluation » Approved-announcement to be sent
"RTP Topologies", Magnus Westerlund, Stephan Wenger, 26-Oct-07 TXT HTML PDF
Abstract: This document discusses multi-endpoint topologies used in Real-time Transport Protocol (RTP)-based environments. In particular, centralized topologies commonly employed in the video conferencing industry are mapped to the RTP terminology.
State: Approved-announcement to be sent
ID Tracker » ATOM
Document details »
AVT WG »
- draft-ietf-behave-p2p-state : IESG Evaluation » IESG Evaluation - Defer
"State of Peer-to-Peer(P2P) Communication Across Network Address Translators(NATs)", Pyda Srisuresh, Bryan Ford, Dan Kegel, 16-Oct-07 TXT HTML PDF
Abstract: This memo documents the various methods known to be in use by applications to establish direct communication in the presence of Network Address Translators (NATs) at the current time. Although this memo is intended to be mainly descriptive, the Security Considerations section makes some purely advisory recommendations about how to deal with security vulnerabilities the applications could inadvertently create when using the methods described. This memo covers NAT traversal approaches used by both TCP and UDP based applications. This memo is not an endorsement of the methods described, but merely an attempt to capture them in a document.
State: IESG Evaluation - Defer
ID Tracker » ATOM
Document details »
BEHAVE WG »
- draft-ietf-eap-netsel-problem : Waiting for AD Go-Ahead » IESG Evaluation - Defer
"Network Discovery and Selection Problem", Jari Arkko, 5-Jun-07 TXT HTML PDF
Abstract: When multiple access networks are available, users may have difficulty in selecting which network to connect to, and how to authenticate with that network. This document defines the network discovery and selection problem, dividing it into multiple sub- problems. Some constraints on potential solutions are outlined, and the limitations of several solutions (including existing ones) are discussed.
State: IESG Evaluation - Defer
ID Tracker » ATOM
Document details »
EAP WG »
- draft-ietf-ipfix-implementation-guidelines : IESG Evaluation » IESG Evaluation::Revised ID Needed
"IPFIX Implementation Guidelines", Elisa Boschi, 26-Sep-07 TXT HTML PDF
Abstract: The IP Flow Information eXport (IPFIX) protocol defines how IP Flow information can be exported from routers, measurement probes or other devices. This document provides guidelines for the implementation and use of the IPFIX protocol. Several sets of guidelines address template management, transport-specific issues, implementation of exporting and collecting processes and IPFIX implementation on middleboxes (such as firewalls, network address translators, tunnel endpoints, packet classifiers, etc.).
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
IPFIX WG »
- draft-ietf-iptel-tgrep : IESG Evaluation::AD Followup » IESG Evaluation::External Party
"A Telephony Gateway REgistration Protocol (TGREP)", Manjunath Bangalore, 21-Sep-07 TXT HTML PDF
Abstract: This document describes the Telephony Gateway Registration Protocol (TGREP) for registration of telephony prefixes supported by telephony gateways and soft switches [12]. The registration mechanism can also be used to export resource information. The prefix and resource information can then be passed on to a Telephony Routing over IP (TRIP) Location Server, which in turn can propagate that routing information within and between Internet telephony administrative domains (ITAD). TGREP shares a lot of similarities with the TRIP Protocol. It has similar procedures and Finite State Machine for session establishment. It also shares the same format for messages and a subset of attributes with TRIP.
State: IESG Evaluation::External Party
ID Tracker » ATOM
Document details »
IPTEL WG »
- draft-ietf-shim6-proto : AD Evaluation::Revised ID Needed » AD Evaluation::AD Followup
"Shim6: Level 3 Multihoming Shim Protocol for IPv6", Marcelo Bagnulo, Erik Nordmark, 1-Nov-07 TXT HTML PDF
Abstract: This document defines the Shim6 protocol, a layer 3 shim for providing locator agility below the transport protocols, so that multihoming can be provided for IPv6 with failover and load sharing properties, without assuming that a multihomed site will have a provider independent IPv6 address prefix which is announced in the global IPv6 routing table. The hosts in a site which has multiple provider allocated IPv6 address prefixes, will use the Shim6 protocol specified in this document to setup state with peer hosts, so that the state can later be used to failover to a different locator pair, should the original one stop working.
State: AD Evaluation::AD Followup
ID Tracker » ATOM
Document details »
SHIM6 WG »
- draft-ietf-simple-partial-notify : IESG Evaluation - Defer » IESG Evaluation::Revised ID Needed
" Session Initiation Protocol (SIP) extension for Partial Notification of Presence Information", Mikko Lonnfors, 27-Feb-07 TXT HTML PDF
Abstract: By default, presence delivered using the Presence Event Package for the Session Initiation Protocol (SIP) is represented in the Presence Information Data Format (PIDF). A PIDF document contains a set of elements, each representing a different aspect of the presence being reported. When any subset of the elements change, even just a single element, a new document containing the full set of elements is delivered. This memo defines an extension allowing delivery of only the presence data that has actually changed.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
SIMPLE WG »
- draft-ietf-simple-partial-pidf-format : IESG Evaluation - Defer » IESG Evaluation::Revised ID Needed
"Presence Information Data format (PIDF) Extension for Partial Presence", Mikko Lonnfors, 15-Nov-06 TXT HTML PDF
Abstract: The Presence Information Document Format (PIDF) specifies the baseline XML based format for describing presence information. One of the characteristic of the PIDF is that the document always needs to carry all presence information available for the presentity. In some environments where low bandwidth and high latency links can exist it is often beneficial to limit the amount of transported information over the network. This document introduces a new MIME type which enables transporting of either only the changed parts or the full PIDF based presence information.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
SIMPLE WG »
- draft-ietf-simple-partial-publish : IESG Evaluation - Defer » IESG Evaluation::Revised ID Needed
"Publication of Partial Presence Information", Mikko Lonnfors, 7-Feb-07 TXT HTML PDF
Abstract: The Session Initiation Protocol (SIP) Extension for Event State Publication describes a mechanism with which a presence user agent is able to publish presence information to a presence agent. Using the Presence Information Data Format (PIDF), each presence publication contains full state, regardless of how much of that information has actually changed since the previous update. As a consequence, updating a sizeable presence document with small changes bears a considerable overhead and is therefore inefficient. Especially with low bandwidth and high latency links, this can constitue a considerable burden to the system. This memo defines a solution that aids in reducing the impact of those constraints and increases transport efficiency by introducing a mechanism that allows for publication of partial presence information.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
SIMPLE WG »
- draft-ietf-simple-xml-patch-ops : IESG Evaluation - Defer » IESG Evaluation::Revised ID Needed
"An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors", Jari Urpalainen, 9-Aug-07 TXT HTML PDF
Abstract: Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic <add>, <replace> and <remove> directives a set of patches can then be applied to update an existing XML document.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
SIMPLE WG »
- draft-ietf-smime-cades : In Last Call » Waiting for AD Go-Ahead
"CMS Advanced Electronic Signatures (CAdES)", John Ross, 18-Oct-07 TXT HTML PDF
Abstract: This document defines the format of an electronic signature that can remain valid over long periods. This includes evidence as to its validity even if the signer or verifying party later attempts to deny (i.e., repudiates the validity of the signature). The format can be considered as an extension to RFC 3852 [4] and RFC 2634 [5], where, when appropriate additional signed and unsigned attributes have been defined. The contents of this Informational RFC amounts to a transposition of the ETSI TS 101 733 V.1.7.3 (CMS Advanced Electronic Signatures - CAdES) [TS101733] and is technically equivalent to it.
State: Waiting for AD Go-Ahead
ID Tracker » ATOM
Document details »
SMIME WG »
- draft-ietf-tsvwg-diffserv-class-aggr : IESG Evaluation » IESG Evaluation::AD Followup
"Aggregation of DiffServ Service Classes", Kwok Ho Chan, Jozef Babiarz, Fred Baker, 30-Oct-07 TXT HTML PDF
Abstract: In the core of a high capacity network, service differentiation may still be needed to support applications' utilization of the network. Applications with similar traffic characteristics and performance requirements are mapped into diffserv service classes based on end- to-end behavior requirements of the applications. However, some network segments may be configured in such a way that a single forwarding treatment may satisfy the traffic characteristics and performance requirements of two or more service classes. In these cases, it may be desirable to aggregate two or more diffserv service classes into a single forwarding treatment. This document provides guidelines for the aggregation of diffserv service classes into forwarding treatments.
State: IESG Evaluation::AD Followup
ID Tracker » ATOM
Document details »
TSVWG WG »
- draft-ietf-tsvwg-ecn-mpls : IESG Evaluation » IESG Evaluation - Defer
"Explicit Congestion Marking in MPLS", Bruce Davie, Bob Briscoe, June Tay, 4-Oct-07 TXT HTML PDF
Abstract: RFC 3270 defines how to support the Diffserv architecture in MPLS networks, including how to encode Diffserv Code Points (DSCPs) in an MPLS header. DSCPs may be encoded in the EXP field, while other uses of that field are not precluded. RFC3270 makes no statement about how Explicit Congestion Notification (ECN) marking might be encoded in the MPLS header. This draft defines how an operator might define some of the EXP codepoints for explicit congestion notification, without precluding other uses.
State: IESG Evaluation - Defer
ID Tracker » ATOM
Document details »
TSVWG WG »
- draft-ietf-v6ops-scanning-implications : IESG Evaluation » IESG Evaluation::Revised ID Needed
"IPv6 Implications for Network Scanning", Tim Chown, 28-Mar-07 TXT HTML PDF
Abstract: The 128 bits of IPv6 address space is considerably bigger than the 32 bits of address space of IPv4. In particular, the IPv6 subnets to which hosts attach will by default have 64 bits of host address space. As a result, traditional methods of remote TCP or UDP network scanning to discover open or running services on a host will potentially become less feasible, due to the larger search space in the subnet. In addition automated attacks, such as those performed by network worms, that pick random host addresses to propagate to, may be hampered. This document discusses this property of IPv6 and describes related issues for IPv6 site network administrators to consider, which may be of importance when planning site address allocation and management strategies. While traditional network scanning probes (whether by individuals or automated via network worms) may become less common, administrators should be aware of other methods attackers may use to discover IPv6 addresses on a target network, and also be aware of appropriate measures to mitigate them.
State: IESG Evaluation::Revised ID Needed
ID Tracker » ATOM
Document details »
V6OPS WG »
- draft-ietf-xcon-framework : IESG Evaluation » IESG Evaluation - Defer
"A Framework for Centralized Conferencing", Mary Barnes, 6-Aug-07 TXT HTML PDF
Abstract: This document defines the framework for Centralized Conferencing. The framework allows participants using various call signaling protocols, such as SIP, H.323, Jabber, Q.931 or ISUP, to exchange media in a centralized unicast conference. The Centralized Conferencing Framework defines logical entities and naming conventions, along with a high level conferencing data model. The framework also outlines a set of conferencing protocols, which are complementary to the call signaling protocols, for building advanced conferencing applications. The framework binds all the defined components together for the benefit of builders of conferencing systems.
State: IESG Evaluation - Defer
ID Tracker » ATOM
Document details »
XCON WG »
- draft-malis-sonet-ces-mpls : Waiting for AD Go-Ahead » Approved-announcement to be sent::Point Raised - writeup needed
"SONET/SDH Circuit Emulation Service over MPLS (CEM) Encapsulation", Andrew Malis, 17-Aug-07 TXT HTML PDF
Abstract: This document describes a historical method for encapsulating SONET/SDH Path signals for transport across packet-switched networks (PSNs). The PSNs explicitly supported by this document include MPLS and IP. Note that [RFC4842] describes the standards-track protocol for this functionality, and new implementations must use [RFC4842] rather than this document except when interoperability with older implementations is desired.
State: Approved-announcement to be sent::Point Raised - writeup needed
ID Tracker » ATOM
- draft-saintandre-rfc4622bis : Waiting for Writeup » Approved-announcement to be sent
"Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) for the Extensible Messaging and Presence Protocol (XMPP)", Peter Saint-Andre, 14-Jun-07 TXT HTML PDF
Abstract: This document defines the use of Internationalized Resource Identifiers (IRIs) and Uniform Resource Identifiers (URIs) in identifying or interacting with entities that can communicate via the Extensible Messaging and Presence Protocol (XMPP). This document obsoletes RFC 4622.
State: Approved-announcement to be sent
ID Tracker » ATOM
- draft-wilde-text-fragment : IESG Evaluation::Revised ID Needed » IESG Evaluation::AD Followup
"URI Fragment Identifiers for the text/plain Media Type", Erik Wilde, Martin Duerst, 1-Nov-07 TXT HTML PDF
Abstract: This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust.
State: IESG Evaluation::AD Followup
ID Tracker » ATOM
Drafts Sent to RFC Editor
- draft-ietf-mmusic-ice : was in Approved-announcement sent
"Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols", Jonathan Rosenberg, 29-Oct-07 TXT HTML PDF
Abstract: This document describes a protocol for Network Address Translator (NAT) traversal for UDP-based multimedia sessions established with the offer/answer model. This protocol is called Interactive Connectivity Establishment (ICE). ICE makes use of the Session Traversal Utilities for NAT (STUN) protocol and its extension, Traversal Using Relay NAT (TURN). ICE can be used by any protocol utilizing the offer/answer model, such as the Session Initiation Protocol (SIP).
State: RFC Ed Queue
ID Tracker » ATOM
Document details »
MMUSIC WG »
RFC Editor Queue »
RFC Editor Queue History »
- draft-ietf-tsvwg-udplite-mib : was in Approved-announcement sent
"MIB for the UDP-Lite protocol", Gerrit Renker, Gorry Fairhurst, 29-Oct-07 TXT HTML PDF
Abstract: This document specifies a Management Information Base (MIB) module for the Lightweight User Datagram Protocol. It defines a set of new MIB objects to characterise the behaviour and performance of transport layer endpoints deploying UDP-Lite. UDP-Lite resembles UDP, but differs from the semantics of UDP by the addition of a single option. This adds the capability for variable-length data checksum coverage, which can benefit a class of applications that prefer delivery of (partially) corrupted datagram payload data in preference to discarding the datagram.
State: RFC Ed Queue
ID Tracker » ATOM
Document details »
TSVWG WG »
RFC Editor Queue »
RFC Editor Queue History »
Other Status Changes
IANA Progress
- enterprise-numbers : updated
- multicast-addresses : updated
- sieve-extensions : updated
- trip-parameters : updated
- uri-schemes.html : updated
- media-types/application/index.html : updated
- uri-schemes/prov/pack : new file