headers
internet-drafts | 1 Aug 2012 01:26
Picon
Favicon

I-D Action: draft-ietf-dime-pmip6-lr-17.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Diameter Maintenance and Extensions Working Group of the IETF.

	Title           : Diameter Support for Proxy Mobile IPv6 Localized Routing
	Author(s)       : Glen Zorn
                          Qin Wu
                          Jouni Korhonen
	Filename        : draft-ietf-dime-pmip6-lr-17.txt
	Pages           : 12
	Date            : 2012-07-31

Abstract:
   In Proxy Mobile IPv6, packets received from a Mobile Node (MN) by the
   Mobile Access Gateway (MAG) to which it is attached are typically
   tunneled to a Local Mobility Anchor (LMA) for routing.  The term
   "localized routing" refers to a method by which packets are routed
   directly between an MN's MAG and the MAG of its Correspondent Node
   (CN) without involving any LMA.  In a Proxy Mobile IPv6 deployment,
   it may be desirable to control the establishment of localized routing
   sessions between two MAGs in a Proxy Mobile IPv6 domain by requiring
   that the session be authorized.  This document specifies how to
   accomplish this using the Diameter protocol.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dime-pmip6-lr

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dime-pmip6-lr-17
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 01:48
Picon
Favicon

I-D Action: draft-ietf-6man-impatient-nud-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

	Title           : Neighbor Unreachability Detection is too impatient
	Author(s)       : Erik Nordmark
                          Igor Gashinsky
	Filename        : draft-ietf-6man-impatient-nud-02.txt
	Pages           : 8
	Date            : 2012-07-31

Abstract:
   IPv6 Neighbor Discovery includes Neighbor Unreachability Detection.
   That function is very useful when a host has an alternative, for
   instance multiple default routers, since it allows the host to switch
   to the alternative in short time.  This time is 3 seconds after the
   node starts probing by default.  However, if there are no
   alternatives, this is far too impatient.  This document specifies
   relaxed rules for Neighbor Discovery retransmissions that allows an
   implementation to choose different timeout behavior based on whether
   or not there are alternatives.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-impatient-nud

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-impatient-nud-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-impatient-nud-02
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 02:12
Picon
Favicon

I-D Action: draft-richardson-roll-applicability-template-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : ROLL Applicability Statement Template
	Author(s)       : Michael C. Richardson
	Filename        : draft-richardson-roll-applicability-template-00.txt
	Pages           : 15
	Date            : 2012-07-31

Abstract:
   This document is a template applicability statement for the Routing
   over Low-power and Lossy Networks (ROLL) WG.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-richardson-roll-applicability-template

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-richardson-roll-applicability-template-00

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 02:16
Picon
Favicon

I-D Action: draft-hallambaker-scijer-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Simple Cloud Interoperable Jason Encoding for REST Web Services (SCIJER) Bindings
	Author(s)       : Phillip Hallam-Baker
	Filename        : draft-hallambaker-scijer-00.txt
	Pages           : 7
	Date            : 2012-07-31

Abstract:
   SCIJER (pronounced skyjer) specifies a mapping of data types to
   JavaScript Object Notation (JSON) encoding.  The JSON specification
   defines encodings for integers, strings, arrays and objects.  This
   document specifies a mapping between JSON encoding and an extended
   set of types.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-hallambaker-scijer

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-hallambaker-scijer-00

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 02:23
Picon
Favicon

I-D Action: draft-bormann-coap-misc-20.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Miscellaneous additions to CoAP
	Author(s)       : Carsten Bormann
                          Klaus Hartke
	Filename        : draft-bormann-coap-misc-20.txt
	Pages           : 56
	Date            : 2012-07-31

Abstract:
   This short I-D makes a number of partially interrelated proposals how
   to solve certain problems in the CoRE WG's main protocol, the
   Constrained Application Protocol (CoAP).  The current version has
   been resubmitted to keep information about these proposals available;
   the proposals are not all fleshed out at this point in time.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bormann-coap-misc

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-bormann-coap-misc-20

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-bormann-coap-misc-20

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 02:25
Picon
Favicon

I-D Action: draft-ietf-eai-rfc5721bis-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Email Address Internationalization Working Group of the IETF.

	Title           : POP3 Support for UTF-8
	Author(s)       : Randall Gellens
                          Chris Newman
                          Jiankang Yao
                          Kazunori Fujiwara
	Filename        : draft-ietf-eai-rfc5721bis-07.txt
	Pages           : 14
	Date            : 2012-07-31

Abstract:
   This specification extends the Post Office Protocol version 3 (POP3)
   to support UTF-8 encoded international string in user names,
   passwords, mail addresses, message headers, and protocol-level
   textual strings.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-eai-rfc5721bis

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-eai-rfc5721bis-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-eai-rfc5721bis-07

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 02:53
Picon
Favicon

I-D Action: draft-bormann-core-congestion-control-02.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Congestion Control Principles for CoAP
	Author(s)       : Carsten Bormann
                          Klaus Hartke
	Filename        : draft-bormann-core-congestion-control-02.txt
	Pages           : 22
	Date            : 2012-07-31

Abstract:
   The CoAP protocol needs to be implemented in such a way that it does
   not cause persistent congestion on the network it uses.  Congestion
   control is a complex issue -- the proper rationale for the congestion
   control mechanisms chosen in CoAP is probably more material than the
   CoAP protocol specification itself.  This informational document
   attempts to pull out the background material and more extensive
   considerations behind the CoAP congestion control mechanisms, while
   leaving the basic MUSTs and MUST NOTs in the main spec.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-bormann-core-congestion-control

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-bormann-core-congestion-control-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-bormann-core-congestion-control-02

Internet-Drafts are also available by anonymous FTP at:
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 08:23
Picon
Favicon

I-D Action: draft-leiba-cotton-iana-5226bis-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Guidelines for Writing an IANA Considerations Section in RFCs
	Author(s)       : Michelle Cotton
                          Barry Leiba
                          Thomas Narten
	Filename        : draft-leiba-cotton-iana-5226bis-00.txt
	Pages           : 36
	Date            : 2012-07-31

Abstract:
   Many protocols make use of identifiers consisting of constants and
   other well-known values.  Even after a protocol has been defined and
   deployment has begun, new values may need to be assigned (such as for
   a new option type in DHCP, or a new encryption or authentication
   transform for IPsec).  To ensure that such quantities have consistent
   values and interpretations across all implementations, their
   assignment must be administered by a central authority.  For IETF
   protocols, that role is provided by the Internet Assigned Numbers
   Authority (IANA).

   In order for IANA to manage a given namespace prudently, it needs
   guidelines describing the conditions under which new values can be
   assigned or when modifications to existing values can be made.  If
   IANA is expected to play a role in the management of a namespace,
   IANA must be given clear and concise instructions describing that
   role.  This document discusses issues that should be considered in
   formulating a policy for assigning values to a namespace and provides
   guidelines for authors on the specific text that must be included in
(Continue reading)

Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 08:31
Picon
Favicon

I-D Action: draft-baryun-rfc2119-update-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Key Words of Conditional Language of Requirements Levels
	Author(s)       : Abdussalam Nuri Baryun
	Filename        : draft-baryun-rfc2119-update-00.txt
	Pages           : 3
	Date            : 2012-07-31

Abstract:
   In many standards track documents conditional words are used to
   signify the requirements in the specification. These words are
   prefered to be capitalized. This document defines these conditional
   words as they should be interpreted in IETF documents. Authors who
   follow these guidelines should incorporate this phrase near the
   beginning of their document. The additional key words to words
   described in RFC2119 are; "IF, THEN", "ELSE IF", "ELSE".

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-baryun-rfc2119-update

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-baryun-rfc2119-update-00

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
Permalink | Reply | 0 comments |
headers
internet-drafts | 1 Aug 2012 09:00
Picon
Favicon

I-D Action: draft-balaji-mpls-lawful-intercept-thru-label-dis-01.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.

	Title           : Label-based Provider-Provisioned Lawful Intercept for L3 VPNs
	Author(s)       : Shankar Raman
                          Balaji Venkat Venkataswami
                          Gaurav Raina
                          Vasan Srini
                          Bhargav Bhikkaji
	Filename        : draft-balaji-mpls-lawful-intercept-thru-label-dis-01.txt
	Pages           : 12
	Date            : 2012-07-31

Abstract:
   In models of Single-AS and inter-provider Multi- Protocol Label
   Switching (MPLS) based Virtual Private Networks (VPNs) Lawful
   Intercept is a key requirement. For example, MPLS-based Layer 3 VPN
   models do not have any provider provisioned methods of lawful
   intercept that are comprehensive, quick and easy to provision from
   one single point. More particularly the auto-provisioning of lawful
   intercept for all sets of streams travelling between VPN sites and
   consequent re-direction of these streams to the appropriate
   government network has not been covered without multiple instances of
   having to configure the intercept at various points in the network
   both in the Single-AS case and the Inter-Provider VPN case.

   In this paper, we propose a technique which uses a set of pre-defined
   labels called Lawful Intercept labels and a method for provisioning
   lawful intercept amongst the various PE devices using these labels
   both in the Single-AS and the inter-provider VPN cases. A single
(Continue reading)

Permalink | Reply | 0 comments |

Gmane