
From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:16:08 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA6912960D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:16:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACDVGjOBHj_k for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:16:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9638312953D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:16:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 06CB8B81991; Tue,  7 Mar 2017 14:16:01 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0C77CB81990; Tue,  7 Mar 2017 14:16:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221600.0C77CB81990@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:16:00 -0800 (PST)
Subject: [rfc-dist] RFC 8083 on Multimedia Congestion Control: Circuit Breakers for Unicast RTP Sessions
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8083

        Title:      Multimedia Congestion Control: Circuit Breakers 
                    for Unicast RTP Sessions 
        Author:     C. Perkins, V. Singh
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    csp@csperkins.org, 
                    varun@callstats.io
        Pages:      25
        Characters: 67197
        Updates:    RFC 3550

        I-D Tag:    draft-ietf-avtcore-rtp-circuit-breakers-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8083

        DOI:        10.17487/RFC8083

The Real-time Transport Protocol (RTP) is widely used in telephony,
video conferencing, and telepresence applications.  Such applications
are often run on best-effort UDP/IP networks.  If congestion control
is not implemented in these applications, then network congestion can
lead to uncontrolled packet loss and a resulting deterioration of the
user's multimedia experience.  The congestion control algorithm acts
as a safety measure by stopping RTP flows from using excessive
resources and protecting the network from overload.  At the time of
this writing, however, while there are several proprietary solutions,
there is no standard algorithm for congestion control of interactive
RTP flows.

This document does not propose a congestion control algorithm.  It
instead defines a minimal set of RTP circuit breakers: conditions
under which an RTP sender needs to stop transmitting media data to
protect the network from excessive congestion.  It is expected that,
in the absence of long-lived excessive congestion, RTP applications
running on best-effort IP networks will be able to operate without
triggering these circuit breakers.  To avoid triggering the RTP
circuit breaker, any Standards Track congestion control algorithms
defined for RTP will need to operate within the envelope set by these
RTP circuit breaker algorithms.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:16:47 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F64C129618 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:16:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OKukoGK1hdDC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:16:34 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EADE129604 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:16:24 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 71DD3B8199B; Tue,  7 Mar 2017 14:16:21 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 58687B81999; Tue,  7 Mar 2017 14:16:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221620.58687B81999@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:16:20 -0800 (PST)
Subject: [rfc-dist] BCP 208, RFC 8084 on Network Transport Circuit Breakers
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        BCP 208        
        RFC 8084

        Title:      Network Transport Circuit Breakers 
        Author:     G. Fairhurst
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    gorry@erg.abdn.ac.uk
        Pages:      24
        Characters: 61712
        See Also:   BCP 208

        I-D Tag:    draft-ietf-tsvwg-circuit-breaker-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8084

        DOI:        10.17487/RFC8084

This document explains what is meant by the term "network transport                         
Circuit Breaker".  It describes the need for Circuit Breakers (CBs)
for network tunnels and applications when using non-congestion-
controlled traffic and explains where CBs are, and are not, needed.
It also defines requirements for building a CB and the expected
outcomes of using a CB within the Internet.

This document is a product of the Transport Area Working Group Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:17:42 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 549DC129604 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:17:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FY9QvfzEqzKn for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:17:41 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6CCAE129517 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:17:40 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E3096B819A4; Tue,  7 Mar 2017 14:17:38 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 3DBA1B819A0; Tue,  7 Mar 2017 14:17:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221737.3DBA1B819A0@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:17:37 -0800 (PST)
Subject: [rfc-dist] BCP 145, RFC 8085 on UDP Usage Guidelines
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        BCP 145        
        RFC 8085

        Title:      UDP Usage Guidelines 
        Author:     L. Eggert, 
                    G. Fairhurst,
                    G. Shepherd
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    lars@netapp.com, 
                    gorry@erg.abdn.ac.uk, 
                    gjshep@gmail.com
        Pages:      55
        Characters: 145359
        Obsoletes:  RFC 5405
        See Also:   BCP 145

        I-D Tag:    draft-ietf-tsvwg-rfc5405bis-19.txt

        URL:        https://www.rfc-editor.org/info/rfc8085

        DOI:        10.17487/RFC8085

The User Datagram Protocol (UDP) provides a minimal message-passing
transport that has no inherent congestion control mechanisms.  This
document provides guidelines on the use of UDP for the designers of
applications, tunnels, and other protocols that use UDP.  Congestion
control guidelines are a primary focus, but the document also
provides guidance on other topics, including message sizes,
reliability, checksums, middlebox traversal, the use of Explicit
Congestion Notification (ECN), Differentiated Services Code Points
(DSCPs), and ports.

Because congestion control is critical to the stable operation of the
Internet, applications and other protocols that choose to use UDP as
an Internet transport must employ mechanisms to prevent congestion
collapse and to establish some degree of fairness with concurrent
traffic.  They may also need to implement additional mechanisms,
depending on how they use UDP.

Some guidance is also applicable to the design of other protocols
(e.g., protocols layered directly on IP or via IP-based tunnels),
especially when these protocols do not themselves provide congestion
control.

This document obsoletes RFC 5405 and adds guidelines for multicast
UDP usage.

This document is a product of the Transport Area Working Group Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:18:14 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33D4512961E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CvYRhQSldlDA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E10DF129634 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:18:06 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 63CA8B819AD; Tue,  7 Mar 2017 14:18:05 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0A9E0B819AB; Tue,  7 Mar 2017 14:18:04 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221804.0A9E0B819AB@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:18:04 -0800 (PST)
Subject: [rfc-dist] RFC 8086 on GRE-in-UDP Encapsulation
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8086

        Title:      GRE-in-UDP Encapsulation 
        Author:     L. Yong, Ed.,
                    E. Crabbe, 
                    X. Xu,
                    T. Herbert
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    lucy.yong@huawei.com, 
                    edward.crabbe@gmail.com, 
                    xuxiaohu@huawei.com,
                    tom@herbertland.com
        Pages:      27
        Characters: 58743
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-gre-in-udp-encap-19.txt

        URL:        https://www.rfc-editor.org/info/rfc8086

        DOI:        10.17487/RFC8086

This document specifies a method of encapsulating network protocol
packets within GRE and UDP headers.  This GRE-in-UDP encapsulation
allows the UDP source port field to be used as an entropy field.
This may be used for load-balancing of GRE traffic in transit
networks using existing Equal-Cost Multipath (ECMP) mechanisms.
There are two applicability scenarios for GRE-in-UDP with different
requirements: (1) general Internet and (2) a traffic-managed
controlled environment.  The controlled environment has less
restrictive requirements than the general Internet.

This document is a product of the Transport Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:18:38 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E71E129655 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mtERNyFNnmyc for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:18:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55D1E12964C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:18:21 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D15C1B819B4; Tue,  7 Mar 2017 14:18:16 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 387A5B819B3; Tue,  7 Mar 2017 14:18:15 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221815.387A5B819B3@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:18:15 -0800 (PST)
Subject: [rfc-dist] RFC 8087 on The Benefits of Using Explicit Congestion Notification (ECN)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, aqm@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8087

        Title:      The Benefits of Using Explicit 
                    Congestion Notification (ECN) 
        Author:     G. Fairhurst, M. Welzl
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    gorry@erg.abdn.ac.uk, 
                    michawe@ifi.uio.no
        Pages:      19
        Characters: 46449
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-aqm-ecn-benefits-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8087

        DOI:        10.17487/RFC8087

The goal of this document is to describe the potential benefits of
applications using a transport that enables Explicit Congestion
Notification (ECN).  The document outlines the principal gains in
terms of increased throughput, reduced delay, and other benefits when
ECN is used over a network path that includes equipment that supports
Congestion Experienced (CE) marking.  It also discusses challenges
for successful deployment of ECN.  It does not propose new algorithms
to use ECN nor does it describe the details of implementation of ECN
in endpoint devices (Internet hosts), routers, or other network
devices.

This document is a product of the Active Queue Management and Packet Scheduling Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:19:17 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83A8D129657 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:19:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GdIGUT9xJaTs for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:19:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE225129658 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:18:40 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 41287B819A4; Tue,  7 Mar 2017 14:18:39 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 0675EB819B9; Tue,  7 Mar 2017 14:18:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221838.0675EB819B9@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:18:38 -0800 (PST)
Subject: [rfc-dist] RFC 8095 on Services Provided by IETF Transport Protocols and Congestion Control Mechanisms
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, taps@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8095

        Title:      Services Provided by IETF Transport 
                    Protocols and Congestion Control Mechanisms 
        Author:     G. Fairhurst, Ed.,
                    B. Trammell, Ed.,
                    M. Kuehlewind, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    gorry@erg.abdn.ac.uk, 
                    ietf@trammell.ch, 
                    mirja.kuehlewind@tik.ee.ethz.ch
        Pages:      54
        Characters: 126843
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-taps-transports-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8095

        DOI:        10.17487/RFC8095

This document describes, surveys, and classifies the protocol
mechanisms provided by existing IETF protocols, as background for
determining a common set of transport services.  It examines the
Transmission Control Protocol (TCP), Multipath TCP, the Stream
Control Transmission Protocol (SCTP), the User Datagram Protocol
(UDP), UDP-Lite, the Datagram Congestion Control Protocol (DCCP), the
Internet Control Message Protocol (ICMP), the Real-Time Transport
Protocol (RTP), File Delivery over Unidirectional Transport /
Asynchronous Layered Coding (FLUTE/ALC) for Reliable Multicast, NACK-
Oriented Reliable Multicast (NORM), Transport Layer Security (TLS),
Datagram TLS (DTLS), and the Hypertext Transport Protocol (HTTP),
when HTTP is used as a pseudotransport.  This survey provides
background for the definition of transport services within the TAPS
working group.

This document is a product of the Transport Services Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar  7 14:19:23 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3FBF129655 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y91GbQOOKkvy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue,  7 Mar 2017 14:19:21 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 55FF2129649 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue,  7 Mar 2017 14:18:55 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A67F1B819B5; Tue,  7 Mar 2017 14:18:52 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 1D8FFB819B9; Tue,  7 Mar 2017 14:18:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170307221851.1D8FFB819B9@rfc-editor.org>
Date: Tue,  7 Mar 2017 14:18:51 -0800 (PST)
Subject: [rfc-dist] RFC 8108 on Sending Multiple RTP Streams in a Single RTP Session
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8108

        Title:      Sending Multiple RTP Streams in 
                    a Single RTP Session 
        Author:     J. Lennox, M. Westerlund,
                    Q. Wu, C. Perkins
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    jonathan@vidyo.com, 
                    magnus.westerlund@ericsson.com, 
                    bill.wu@huawei.com,  
                    csp@csperkins.org
        Pages:      29
        Characters: 74580
        Updates:    RFC 3550, RFC 4585

        I-D Tag:    draft-ietf-avtcore-rtp-multi-stream-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8108

        DOI:        10.17487/RFC8108

This memo expands and clarifies the behavior of Real-time Transport
Protocol (RTP) endpoints that use multiple synchronization sources
(SSRCs).  This occurs, for example, when an endpoint sends multiple
RTP streams in a single RTP session.  This memo updates RFC 3550 with
regard to handling multiple SSRCs per endpoint in RTP sessions, with
a particular focus on RTP Control Protocol (RTCP) behavior.  It also
updates RFC 4585 to change and clarify the calculation of the timeout
of SSRCs and the inclusion of feedback messages.

This document is a product of the Audio/Video Transport Core Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar  8 19:30:07 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414B6129722 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  8 Mar 2017 19:30:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dv0OjFc6AT1e for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed,  8 Mar 2017 19:30:06 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E0BD120727 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed,  8 Mar 2017 19:30:06 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1E4D8B8103C; Wed,  8 Mar 2017 19:30:01 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id B8D57B8103B; Wed,  8 Mar 2017 19:29:59 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170309032959.B8D57B8103B@rfc-editor.org>
Date: Wed,  8 Mar 2017 19:29:59 -0800 (PST)
Subject: [rfc-dist] RFC 8107 on Advertising Digital Identifier (Ad-ID) URN Namespace Definition
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8107

        Title:      Advertising Digital Identifier (Ad-ID) URN 
                    Namespace Definition 
        Author:     J. Wold
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    jwold@ad-id.org
        Pages:      7
        Characters: 11060
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-adid-urn-03.txt

        URL:        https://www.rfc-editor.org/info/rfc8107

        DOI:        10.17487/RFC8107

Advertising Digital Identifiers (Ad-IDs) are used to 
identify advertising assets across all media platforms.  This
document defines the formal Uniform Resource Name (URN) Namespace
Identifier (NID) "adid" for Ad-IDs.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar  9 18:36:36 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0593A12943B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NkmNPAjLgfg for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1AE01294A6 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9D26EB8023C; Thu,  9 Mar 2017 18:06:33 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 9B96AB8020A; Thu,  9 Mar 2017 18:06:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020631.9B96AB8020A@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:31 -0800 (PST)
Subject: [rfc-dist] RFC 8100 on Diffserv-Interconnection Classes and Practice
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8100

        Title:      Diffserv-Interconnection Classes and Practice 
        Author:     R. Geib, Ed.,
                    D. Black
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    Ruediger.Geib@telekom.de, 
                    david.black@dell.com
        Pages:      21
        Characters: 50264
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-diffserv-intercon-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8100

        DOI:        10.17487/RFC8100

This document defines a limited common set of Diffserv Per-Hop
Behaviors (PHBs) and Diffserv Codepoints (DSCPs) to be applied at
(inter)connections of two separately administered and operated
networks, and it explains how this approach can simplify network
configuration and operation.  Many network providers operate
Multiprotocol Label Switching (MPLS) using Treatment Aggregates for
traffic marked with different Diffserv Per-Hop Behaviors and use MPLS
for interconnection with other networks.  This document offers a
simple interconnection approach that may simplify operation of
Diffserv for network interconnection among providers that use MPLS
and apply the Short Pipe Model.  While motivated by the requirements
of MPLS network operators that use Short Pipe Model tunnels, this
document is applicable to other networks, both MPLS and non-MPLS.

This document is a product of the Transport Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar  9 18:36:38 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FA1D1294CE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wpbj8XYGNafX for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:35 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC5801294B2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 73247B806C4; Thu,  9 Mar 2017 18:07:22 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D83B6B801A3; Thu,  9 Mar 2017 18:07:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020720.D83B6B801A3@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:07:20 -0800 (PST)
Subject: [rfc-dist] RFC 8113 on Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8113

        Title:      Locator/ID Separation Protocol (LISP): Shared 
                    Extension Message & IANA Registry for 
                    Packet Type Allocations 
        Author:     M. Boucadair, C. Jacquenet
        Status:     Experimental
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mohamed.boucadair@orange.com, 
                    christian.jacquenet@orange.com
        Pages:      6
        Characters: 10608
        Updates:    RFC 6830

        I-D Tag:    draft-ietf-lisp-type-iana-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8113

        DOI:        10.17487/RFC8113

This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each
extension.  It also defines a registry for LISP Packet Type
allocations, thus updating RFC 6830.

This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar  9 18:36:39 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56E271294D5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKLXihrmkbmU for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F30C61294C9 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 09DA2B8062E; Thu,  9 Mar 2017 18:06:44 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 08ED8B805C3; Thu,  9 Mar 2017 18:06:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020643.08ED8B805C3@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:43 -0800 (PST)
Subject: [rfc-dist] RFC 8102 on Remote-LFA Node Protection and Manageability
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rtgwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8102

        Title:      Remote-LFA Node Protection and Manageability 
        Author:     P. Sarkar, Ed.,
                    S. Hegde, 
                    C. Bowers,
                    H. Gredler, 
                    S. Litkowski
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pushpasis.ietf@gmail.com, 
                    shraddha@juniper.net, 
                    cbowers@juniper.net,
                    hannes@rtbrick.com, 
                    stephane.litkowski@orange.com
        Pages:      22
        Characters: 50200
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-rlfa-node-protection-13.txt

        URL:        https://www.rfc-editor.org/info/rfc8102

        DOI:        10.17487/RFC8102

The loop-free alternates (LFAs) computed following the current
remote-LFA specification guarantees only link protection.  The
resulting remote-LFA next hops (also called "PQ-nodes") may not
guarantee node protection for all destinations being protected by it.

This document describes an extension to the remote-loop-free-based IP
fast reroute mechanisms that specifies procedures for determining
whether or not a given PQ-node provides node protection for a
specific destination.  The document also shows how the same procedure
can be utilized for the collection of complete characteristics for
alternate paths.  Knowledge about the characteristics of all
alternate paths is a precursor to applying the operator-defined
policy for eliminating paths not fitting the constraints.

This document is a product of the Routing Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar  9 18:41:34 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98DBE1294B2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:41:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p4vWCEeLJlpA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  9 Mar 2017 18:41:33 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47D0C1294FA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  9 Mar 2017 18:41:32 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 387FBB80196; Thu,  9 Mar 2017 18:06:14 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 35E11B80184; Thu,  9 Mar 2017 18:06:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020613.35E11B80184@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:13 -0800 (PST)
Subject: [rfc-dist] RFC 8082 on Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, avtext@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8082

        Title:      Using Codec Control Messages in 
                    the RTP Audio-Visual Profile with Feedback 
                    with Layered Codecs 
        Author:     S. Wenger, J. Lennox,
                    B. Burman, M. Westerlund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    stewe@stewe.org, 
                    jonathan@vidyo.com, 
                    bo.burman@ericsson.com,  
                    magnus.westerlund@ericsson.com
        Pages:      11
        Characters: 25093
        Updates:    RFC 5104

        I-D Tag:    draft-ietf-avtext-avpf-ccm-layered-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8082

        DOI:        10.17487/RFC8082

This document updates RFC 5104 by fixing a shortcoming in the
specification language of the Codec Control Message Full Intra
Request (FIR) description when using it with layered codecs.  In
particular, a decoder refresh point needs to be sent by a media
sender when a FIR is received on any layer of the layered bitstream,
regardless of whether those layers are being sent in a single or in
multiple RTP flows.  The other payload-specific feedback messages
defined in RFC 5104 and RFC 4585 (which was updated by RFC 5506) have
also been analyzed, and no corresponding shortcomings have been
found.

This document is a product of the Audio/Video Transport Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 10 09:23:27 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9416C1296A5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NaT5m8dAVq0 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:23:26 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE2CD1294CF for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 10 Mar 2017 09:23:26 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0D080B80E4F; Fri, 10 Mar 2017 09:23:20 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 31EA1B80E4E; Fri, 10 Mar 2017 09:23:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172319.31EA1B80E4E@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:19 -0800 (PST)
Subject: [rfc-dist] RFC 8078 on Managing DS Records from the Parent via CDS/CDNSKEY
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8078

        Title:      Managing DS Records from the 
                    Parent via CDS/CDNSKEY 
        Author:     O. Gudmundsson, P. Wouters
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    olafur+ietf@cloudflare.com, 
                    pwouters@redhat.com
        Pages:      10
        Characters: 21001
        Updates:    RFC 7344

        I-D Tag:    draft-ietf-dnsop-maintain-ds-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8078

        DOI:        10.17487/RFC8078

RFC 7344 specifies how DNS trust can be maintained across key
rollovers in-band between parent and child.  This document elevates
RFC 7344 from Informational to Standards Track.  It also adds a
method for initial trust setup and removal of a secure entry point.

Changing a domain's DNSSEC status can be a complicated matter
involving multiple unrelated parties.  Some of these parties, such as
the DNS operator, might not even be known by all the organizations
involved.  The inability to disable DNSSEC via in-band signaling is
seen as a problem or liability that prevents some DNSSEC adoption at
a large scale.  This document adds a method for in-band signaling of
these DNSSEC status changes.

This document describes reasonable policies to ease deployment of the
initial acceptance of new secure entry points (DS records).

It is preferable that operators collaborate on the transfer or move
of a domain.  The best method is to perform a Key Signing Key (KSK)
plus Zone Signing Key (ZSK) rollover.  If that is not possible, the
method using an unsigned intermediate state described in this
document can be used to move the domain between two parties.  This
leaves the domain temporarily unsigned and vulnerable to DNS
spoofing, but that is preferred over the alternative of validation
failures due to a mismatched DS and DNSKEY record.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 10 09:24:01 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 845B71299AC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lLyIfM8RtX1a for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:00 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 600231299A4 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 10 Mar 2017 09:23:46 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 773EEB80E57; Fri, 10 Mar 2017 09:23:31 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 81BE8B80E56; Fri, 10 Mar 2017 09:23:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172330.81BE8B80E56@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:30 -0800 (PST)
Subject: [rfc-dist] RFC 8117 on Current Hostname Practice Considered Harmful
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, int-area@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8117

        Title:      Current Hostname Practice Considered Harmful 
        Author:     C. Huitema, D. Thaler, R. Winter
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    huitema@huitema.net, 
                    dthaler@microsoft.com, 
                    rolf.winter@hs-augsburg.de
        Pages:      12
        Characters: 26750
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-intarea-hostname-practice-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8117

        DOI:        10.17487/RFC8117

Giving a hostname to your computer and publishing it as you roam from
one network to another is the Internet's equivalent of walking around
with a name tag affixed to your lapel.  This current practice can
significantly compromise your privacy, and something should change in
order to mitigate these privacy threats.

There are several possible remedies, such as fixing a variety of
protocols or avoiding disclosing a hostname at all.  This document
describes some of the protocols that reveal hostnames today and
sketches another possible remedy, which is to replace static
hostnames by frequently changing randomized values.

This document is a product of the Internet Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 10 09:24:34 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C081299CA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xUMIv-Kquud8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:28 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 914841299A4 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 10 Mar 2017 09:24:01 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id DCDAFB80E5E; Fri, 10 Mar 2017 09:23:41 -0800 (PST)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7F541B80E5C; Fri, 10 Mar 2017 09:23:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172340.7F541B80E5C@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:40 -0800 (PST)
Subject: [rfc-dist] RFC 8128 on IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8128

        Title:      IETF Appointment Procedures for the 
                    ICANN Root Zone Evolution Review Committee 
        Author:     C. Morgan
        Status:     Informational
        Stream:     IAB
        Date:       March 2017
        Mailbox:    cmorgan@amsl.com
        Pages:      5
        Characters: 9416
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-rzerc-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8128

        DOI:        10.17487/RFC8128

This memo outlines the process by which the IETF makes an appointment
to the ICANN Root Zone Evolution Review Committee (RZERC).

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 21:25:43 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C18D01289C3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 21:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NmQMAoW0vz6t for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 21:25:42 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5585128954 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 21:25:42 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BB4E7B8125E; Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 15E48B8125D; Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170315042530.15E48B8125D@rfc-editor.org>
Date: Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
Subject: [rfc-dist] RFC 8097 on BGP Prefix Origin Validation State Extended Community
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, sidr@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8097

        Title:      BGP Prefix Origin Validation State 
                    Extended Community 
        Author:     P. Mohapatra, 
                    K. Patel,
                    J. Scudder, 
                    D. Ward,
                    R. Bush
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mpradosh@yahoo.com, 
                    keyur@arrcus.com, 
                    jgs@juniper.net,  
                    dward@cisco.com, 
                    randy@psg.com
        Pages:      6
        Characters: 12287
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-origin-validation-signaling-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8097

        DOI:        10.17487/RFC8097

This document defines a new BGP opaque extended community to carry
the origination Autonomous System (AS) validation state inside an
autonomous system.  Internal BGP (IBGP) speakers that receive this
validation state can configure local policies that allow it to
influence their decision process.

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:27:27 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D99F112945C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:27:27 -0700 (PDT)
X-Quarantine-ID: <sGVDNGDf-ycu>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGVDNGDf-ycu for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:27:26 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65361129458 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:27:26 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 8D2FBB800F6; Tue, 14 Mar 2017 22:27:14 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 45D99B800F5; Tue, 14 Mar 2017 22:27:13 -0700 (PDT)
X-Quarantine-ID: <hC9YQWayVX2z>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hC9YQWayVX2z; Tue, 14 Mar 2017 22:27:09 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id F4070B800C3; Tue, 14 Mar 2017 22:27:08 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=40966 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Sn-00023P-9e; Wed, 15 Mar 2017 05:27:09 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5R8tP028300; Wed, 15 Mar 2017 05:27:08 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <sidr-bounces@ietf.org>) id 1co0WM-0006ur-Dt for daniel@afrinic.net; Wed, 15 Mar 2017 04:26:54 +0000
Received: from mail.ietf.org ([4.31.198.44]:59608) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <sidr-bounces@ietf.org>) id 1co0WL-0004Se-Q0 for daniel@afrinic.net; Wed, 15 Mar 2017 04:26:46 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35600128BB6; Tue, 14 Mar 2017 21:25:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489551947; bh=7+GbyxquPrrbHxSH75N80pfv55La2py20FGj18lwrlY=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=oYCH6W1j+0qKupY8CDz+jjIhT9sSGeCPJngmNAviCSZerdZL2Cn+RNcplRd+GqONe i65fZvPJ95+BMZlKCSJanFBTE3WqDmS9uXaR7M7LpZWRJJtJIyL7rTpZuiAZYmM7YX bxV3ZQ86P1W3AuIvKRzTVMcJ0v6cAQ6px6HQeTPU=
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD98128896; Tue, 14 Mar 2017 21:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMFmtkb-xmIj; Tue, 14 Mar 2017 21:25:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8B27127B31; Tue, 14 Mar 2017 21:25:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 15E48B8125D; Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170315042530.15E48B8125D@rfc-editor.org>
Date: Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidr/1VB1rJCifgdQ-f9T4TsnlO-8IcA>
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
MIME-Version: 1.0
Subject: [rfc-dist] [sidr] RFC 8097 on BGP Prefix Origin Validation State Extended Community
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, sidr@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8097

        Title:      BGP Prefix Origin Validation State 
                    Extended Community 
        Author:     P. Mohapatra, 
                    K. Patel,
                    J. Scudder, 
                    D. Ward,
                    R. Bush
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mpradosh@yahoo.com, 
                    keyur@arrcus.com, 
                    jgs@juniper.net,  
                    dward@cisco.com, 
                    randy@psg.com
        Pages:      6
        Characters: 12287
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-origin-validation-signaling-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8097

        DOI:        10.17487/RFC8097

This document defines a new BGP opaque extended community to carry
the origination Autonomous System (AS) validation state inside an
autonomous system.  Internal BGP (IBGP) speakers that receive this
validation state can configure local policies that allow it to
influence their decision process.

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:27:45 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3D2C12945E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:27:45 -0700 (PDT)
X-Quarantine-ID: <nKAO0r88c8Av>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nKAO0r88c8Av for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:27:44 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD73F129458 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:27:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0090EB80100; Tue, 14 Mar 2017 22:27:15 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5D1B3B800C3; Tue, 14 Mar 2017 22:27:13 -0700 (PDT)
X-Quarantine-ID: <MMLwEVT0X6XZ>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMLwEVT0X6XZ; Tue, 14 Mar 2017 22:27:09 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id 25A9BB800E6; Tue, 14 Mar 2017 22:27:09 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=40964 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Sm-00023N-4U; Wed, 15 Mar 2017 05:27:08 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5R6It028281; Wed, 15 Mar 2017 05:27:06 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1co0VW-0006um-Qx for daniel@afrinic.net; Wed, 15 Mar 2017 04:26:06 +0000
Received: from mail.ietf.org ([4.31.198.44]:41403) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1co0VV-0004SU-SZ for daniel@afrinic.net; Wed, 15 Mar 2017 04:25:54 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E2D1289B0; Tue, 14 Mar 2017 21:25:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489551943; bh=QJ54zAQ9SKhWszEAAUo/Bb3Vefzx+bXihuSyYf+5M60=; h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To:Cc; b=zDfVciW1ymaoAp/S+xnalFnEa5rDxTckzCcTYIesN7yYaHrZWa2mEiUv0vxt6O+eR vLJOB9zeADdESN4AH03/HOdi1YTr8jQvl3rm2+pcUXhvllQyWCNX+7qr35kximtc2I d6MTladq8CavCj0CN5HTc3DFhla0B2FADIr0m+0g=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD98128896; Tue, 14 Mar 2017 21:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bMFmtkb-xmIj; Tue, 14 Mar 2017 21:25:39 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B8B27127B31; Tue, 14 Mar 2017 21:25:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 15E48B8125D; Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170315042530.15E48B8125D@rfc-editor.org>
Date: Tue, 14 Mar 2017 21:25:30 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/bzHzbkNGkdwTjyWMtR9k-B0Ws20>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
Subject: [rfc-dist] RFC 8097 on BGP Prefix Origin Validation State Extended Community
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, sidr@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8097

        Title:      BGP Prefix Origin Validation State 
                    Extended Community 
        Author:     P. Mohapatra, 
                    K. Patel,
                    J. Scudder, 
                    D. Ward,
                    R. Bush
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mpradosh@yahoo.com, 
                    keyur@arrcus.com, 
                    jgs@juniper.net,  
                    dward@cisco.com, 
                    randy@psg.com
        Pages:      6
        Characters: 12287
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-origin-validation-signaling-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8097

        DOI:        10.17487/RFC8097

This document defines a new BGP opaque extended community to carry
the origination Autonomous System (AS) validation state inside an
autonomous system.  Internal BGP (IBGP) speakers that receive this
validation state can configure local policies that allow it to
influence their decision process.

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:28:17 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61D34129461 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:17 -0700 (PDT)
X-Quarantine-ID: <ZcBzZW8fmllS>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcBzZW8fmllS for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34B9212945F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:28:16 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 703E0B80127; Tue, 14 Mar 2017 22:28:06 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 88F2BB80121; Tue, 14 Mar 2017 22:28:05 -0700 (PDT)
X-Quarantine-ID: <ltlwrfRSUs_p>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ltlwrfRSUs_p; Tue, 14 Mar 2017 22:28:01 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id 5FCD8B80100; Tue, 14 Mar 2017 22:28:01 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41040 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Tj-00025q-IJ; Wed, 15 Mar 2017 05:28:07 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5S6SZ028432; Wed, 15 Mar 2017 05:28:06 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOWR-0003NJ-2t for daniel@afrinic.net; Fri, 10 Mar 2017 17:40:18 +0000
Received: from mail.ietf.org ([4.31.198.44]:45740) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOIw-00077O-Nq for daniel@afrinic.net; Fri, 10 Mar 2017 17:26:15 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2356F1299B3; Fri, 10 Mar 2017 09:24:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489166643; bh=kHZ4adKrlnr8b2TROF1qeNQ1f4yOAJx9IMtY+j1APE8=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=wWWYsN0uyqHTMmW1iAep2O/ox5QYIwJd3QuP2tUe3o6PuOLKKNmYUrldejOs5vQCe vE2+WyacnuLy4bahldPZKpN76Y6G0joY757sG/IFfsY2ndh5fiGNG0b9Anmuqundx4 AQhN3EainCXPAwHT7By8xnNAfQEY/MVl+Vl71wzg=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26E9E1299A5 for <ietf-announce@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PZawLSluaxhu for <ietf-announce@ietfa.amsl.com>; Fri, 10 Mar 2017 09:24:00 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B78E129982 for <ietf-announce@ietf.org>; Fri, 10 Mar 2017 09:23:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7F541B80E5C; Fri, 10 Mar 2017 09:23:40 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172340.7F541B80E5C@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:40 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/DK2vmH27-ivAEJn6mAjK0vBDN8o>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8128 on IETF Appointment Procedures for the ICANN Root Zone Evolution Review Committee
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8128

        Title:      IETF Appointment Procedures for the 
                    ICANN Root Zone Evolution Review Committee 
        Author:     C. Morgan
        Status:     Informational
        Stream:     IAB
        Date:       March 2017
        Mailbox:    cmorgan@amsl.com
        Pages:      5
        Characters: 9416
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-rzerc-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8128

        DOI:        10.17487/RFC8128

This memo outlines the process by which the IETF makes an appointment
to the ICANN Root Zone Evolution Review Committee (RZERC).

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:28:34 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1925B129461 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:34 -0700 (PDT)
X-Quarantine-ID: <4N4f1nvluxgF>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4N4f1nvluxgF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2709612945F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:28:32 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 00EE6B80121; Tue, 14 Mar 2017 22:28:09 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 196C5B80137; Tue, 14 Mar 2017 22:28:07 -0700 (PDT)
X-Quarantine-ID: <JqaGlBqPt5fN>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JqaGlBqPt5fN; Tue, 14 Mar 2017 22:28:03 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id F23CDB8011F; Tue, 14 Mar 2017 22:28:02 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41042 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Tk-000260-NO; Wed, 15 Mar 2017 05:28:08 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5S8lM028436; Wed, 15 Mar 2017 05:28:08 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOWp-0003NW-IR for daniel@afrinic.net; Fri, 10 Mar 2017 17:40:57 +0000
Received: from mail.ietf.org ([4.31.198.44]:40969) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOHr-00076o-Lb for daniel@afrinic.net; Fri, 10 Mar 2017 17:25:08 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CA968129997; Fri, 10 Mar 2017 09:23:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489166639; bh=3XLyREob+D5hm0Ag1UCnrGUWV/iLxHm7pq8VUPaAIB0=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=DHjFbTWPPwft/bfaBu+OnwodM1WBWtNoim32oFeDigFihsEf65onLpSZYBqG/anRG 7gccOKLsGAy54lQHKtHuMt68Ma0iCFklos8maaOtv3nvedHyRx4wPfsx0jfLfxpzRT qxc63wztPOTVmDniJsWkFPS1dAfxFEcRfl1KDuGw=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7151299A7; Fri, 10 Mar 2017 09:23:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tR0ccuNgvQw0; Fri, 10 Mar 2017 09:23:40 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CDCC1299A1; Fri, 10 Mar 2017 09:23:35 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 81BE8B80E56; Fri, 10 Mar 2017 09:23:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172330.81BE8B80E56@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:30 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/5Pkus0dA9PWVafOrPlCfMhzU4_8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8117 on Current Hostname Practice Considered Harmful
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, int-area@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8117

        Title:      Current Hostname Practice Considered Harmful 
        Author:     C. Huitema, D. Thaler, R. Winter
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    huitema@huitema.net, 
                    dthaler@microsoft.com, 
                    rolf.winter@hs-augsburg.de
        Pages:      12
        Characters: 26750
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-intarea-hostname-practice-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8117

        DOI:        10.17487/RFC8117

Giving a hostname to your computer and publishing it as you roam from
one network to another is the Internet's equivalent of walking around
with a name tag affixed to your lapel.  This current practice can
significantly compromise your privacy, and something should change in
order to mitigate these privacy threats.

There are several possible remedies, such as fixing a variety of
protocols or avoiding disclosing a hostname at all.  This document
describes some of the protocols that reveal hostnames today and
sketches another possible remedy, which is to replace static
hostnames by frequently changing randomized values.

This document is a product of the Internet Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:28:49 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A06D129464 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:49 -0700 (PDT)
X-Quarantine-ID: <lOhytSiU07BG>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lOhytSiU07BG for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:28:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEADD129463 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:28:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6B29AB80141; Tue, 14 Mar 2017 22:28:09 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id B915BB8011F; Tue, 14 Mar 2017 22:28:07 -0700 (PDT)
X-Quarantine-ID: <RX4xYPefPLXp>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RX4xYPefPLXp; Tue, 14 Mar 2017 22:28:03 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id 6FBEBB8011A; Tue, 14 Mar 2017 22:28:03 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41044 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Tl-000269-Ki; Wed, 15 Mar 2017 05:28:09 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5S9Eo028440; Wed, 15 Mar 2017 05:28:09 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <dnsop-bounces@ietf.org>) id 1cmOXA-0003NJ-M6 for daniel@afrinic.net; Fri, 10 Mar 2017 17:41:10 +0000
Received: from mail.ietf.org ([4.31.198.44]:60135) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <dnsop-bounces@ietf.org>) id 1cmOHF-00076X-1y for daniel@afrinic.net; Fri, 10 Mar 2017 17:24:29 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3CE1296A5; Fri, 10 Mar 2017 09:23:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489166611; bh=bUnYmvghLoAquj/NJZrw6wHkkVrYni9kA3f4FKtKDrs=; h=To:From:Date:Cc:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe; b=rdYUBDC6OCJ8hOGrmOUOEzrskRWZjBoeVb23cFQA+2yWGv89+njDmmTUl79J5m9A8 yOXJhycNtspmJXXoyJLBNp72d7zsSMtZfYgs1oENrypuMH/rfNaYSMUBmDVaHn9iGF B5dMl1evTXKiSMI8uMEHTD2lHEFdjOpjeujBnteM=
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD1E1296A4; Fri, 10 Mar 2017 09:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIfYBdP5hg16; Fri, 10 Mar 2017 09:23:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C230C1294CF; Fri, 10 Mar 2017 09:23:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 31EA1B80E4E; Fri, 10 Mar 2017 09:23:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172319.31EA1B80E4E@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:19 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/jp9fyhkfbrohfuY-U4CgLIPR3tQ>
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
MIME-Version: 1.0
Subject: [rfc-dist] [DNSOP] RFC 8078 on Managing DS Records from the Parent via	CDS/CDNSKEY
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8078

        Title:      Managing DS Records from the 
                    Parent via CDS/CDNSKEY 
        Author:     O. Gudmundsson, P. Wouters
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    olafur+ietf@cloudflare.com, 
                    pwouters@redhat.com
        Pages:      10
        Characters: 21001
        Updates:    RFC 7344

        I-D Tag:    draft-ietf-dnsop-maintain-ds-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8078

        DOI:        10.17487/RFC8078

RFC 7344 specifies how DNS trust can be maintained across key
rollovers in-band between parent and child.  This document elevates
RFC 7344 from Informational to Standards Track.  It also adds a
method for initial trust setup and removal of a secure entry point.

Changing a domain's DNSSEC status can be a complicated matter
involving multiple unrelated parties.  Some of these parties, such as
the DNS operator, might not even be known by all the organizations
involved.  The inability to disable DNSSEC via in-band signaling is
seen as a problem or liability that prevents some DNSSEC adoption at
a large scale.  This document adds a method for in-band signaling of
these DNSSEC status changes.

This document describes reasonable policies to ease deployment of the
initial acceptance of new secure entry points (DS records).

It is preferable that operators collaborate on the transfer or move
of a domain.  The best method is to perform a Key Signing Key (KSK)
plus Zone Signing Key (ZSK) rollover.  If that is not possible, the
method using an unsigned intermediate state described in this
document can be used to move the domain between two parties.  This
leaves the domain temporarily unsigned and vulnerable to DNS
spoofing, but that is preferred over the alternative of validation
failures due to a mismatched DS and DNSKEY record.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:29:19 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92F46129466 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:29:19 -0700 (PDT)
X-Quarantine-ID: <FRipEFtOTH6M>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRipEFtOTH6M for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:29:18 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A730129469 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:29:09 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0C2ABB80158; Tue, 14 Mar 2017 22:28:11 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 01166B80139; Tue, 14 Mar 2017 22:28:10 -0700 (PDT)
X-Quarantine-ID: <gvDwd8pNkDk4>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gvDwd8pNkDk4; Tue, 14 Mar 2017 22:28:06 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [196.192.112.169]) by rfc-editor.org (Postfix) with ESMTPS id C1735B80100; Tue, 14 Mar 2017 22:28:05 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41046 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1Tm-00026K-VN; Wed, 15 Mar 2017 05:28:11 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5S90Z028444; Wed, 15 Mar 2017 05:28:09 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOXC-0003NW-DK for daniel@afrinic.net; Fri, 10 Mar 2017 17:41:14 +0000
Received: from mail.ietf.org ([4.31.198.44]:54798) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmOGL-00075X-MD for daniel@afrinic.net; Fri, 10 Mar 2017 17:23:34 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BF2581294CF; Fri, 10 Mar 2017 09:23:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489166608; bh=MgOkBuLvt8az9oTPxnI9mrIpaOYXXvVIDzia3UosX0c=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=hksPOTIGYFtN+4hFNmk0P+iUB2OONXMmLeKFTB7VpxJN9xXcCeWfNB8ooRrUVYhcK /HHPDWfESOtdArmZSzwpeAHBRqLDF5s9b/TY1urm+QClndhQude5ZA9ahtkSsSRwab hhzj0U0RSoq2tQCwlnC9JCHAsiHabZCCnxTeQ/9c=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BD1E1296A4; Fri, 10 Mar 2017 09:23:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uIfYBdP5hg16; Fri, 10 Mar 2017 09:23:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C230C1294CF; Fri, 10 Mar 2017 09:23:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 31EA1B80E4E; Fri, 10 Mar 2017 09:23:19 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310172319.31EA1B80E4E@rfc-editor.org>
Date: Fri, 10 Mar 2017 09:23:19 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/gGEUngOAxM6aXD_hVkbKQ8eXdow>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8078 on Managing DS Records from the Parent via CDS/CDNSKEY
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8078

        Title:      Managing DS Records from the 
                    Parent via CDS/CDNSKEY 
        Author:     O. Gudmundsson, P. Wouters
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    olafur+ietf@cloudflare.com, 
                    pwouters@redhat.com
        Pages:      10
        Characters: 21001
        Updates:    RFC 7344

        I-D Tag:    draft-ietf-dnsop-maintain-ds-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8078

        DOI:        10.17487/RFC8078

RFC 7344 specifies how DNS trust can be maintained across key
rollovers in-band between parent and child.  This document elevates
RFC 7344 from Informational to Standards Track.  It also adds a
method for initial trust setup and removal of a secure entry point.

Changing a domain's DNSSEC status can be a complicated matter
involving multiple unrelated parties.  Some of these parties, such as
the DNS operator, might not even be known by all the organizations
involved.  The inability to disable DNSSEC via in-band signaling is
seen as a problem or liability that prevents some DNSSEC adoption at
a large scale.  This document adds a method for in-band signaling of
these DNSSEC status changes.

This document describes reasonable policies to ease deployment of the
initial acceptance of new secure entry points (DS records).

It is preferable that operators collaborate on the transfer or move
of a domain.  The best method is to perform a Key Signing Key (KSK)
plus Zone Signing Key (ZSK) rollover.  If that is not possible, the
method using an unsigned intermediate state described in this
document can be used to move the domain between two parties.  This
leaves the domain temporarily unsigned and vulnerable to DNS
spoofing, but that is preferred over the alternative of validation
failures due to a mismatched DS and DNSKEY record.

This document is a product of the Domain Name System Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:35:59 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B7A129482 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:35:58 -0700 (PDT)
X-Quarantine-ID: <K0veJRrhX2lj>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K0veJRrhX2lj for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:35:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 66E25129495 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:35:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E6737B8013B; Tue, 14 Mar 2017 22:35:45 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id E8CFBB80139; Tue, 14 Mar 2017 22:35:44 -0700 (PDT)
X-Quarantine-ID: <5OOOShxSR3fh>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5OOOShxSR3fh; Tue, 14 Mar 2017 22:35:40 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [196.192.112.169]) by rfc-editor.org (Postfix) with ESMTPS id 958D6B80131; Tue, 14 Mar 2017 22:35:40 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41324 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1b8-0002RP-MI; Wed, 15 Mar 2017 05:35:46 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5ZjmH028982; Wed, 15 Mar 2017 05:35:45 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAQA-00055I-PZ for daniel@afrinic.net; Fri, 10 Mar 2017 02:36:52 +0000
Received: from mail.ietf.org ([4.31.198.44]:38247) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAQ8-0005e5-Rs for daniel@afrinic.net; Fri, 10 Mar 2017 02:36:46 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0900E1294CA; Thu,  9 Mar 2017 18:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489113398; bh=PPfM79iWYcM5o1PT+uNdWwIpfbLe43SYYnBzzaXEyio=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=nyVHGLg6f8sI0VkQ1pUme+mOdnxqGxPcpy8DxTAUvLNNkUpSEm1ViGcPG2oYFvb9p rGmbw0TtAq51MLKkOtDBGyPLPaYknd09OZgW3WebvhY2uW2wGnC4ZbheQ64Z7nEAI6 5VQ4DW7a/bzj67pbN+SwZv0SWeKGSqZ7W59qZPUQ=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDD9A1294CA; Thu,  9 Mar 2017 18:36:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id arvS1_Gh-eNq; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B18AF12943B; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9B96AB8020A; Thu,  9 Mar 2017 18:06:31 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020631.9B96AB8020A@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:31 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/iLyz6uaGd7I2VRU3VTS2Lu-Qqcs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8100 on Diffserv-Interconnection Classes and Practice
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, tsvwg@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8100

        Title:      Diffserv-Interconnection Classes and Practice 
        Author:     R. Geib, Ed.,
                    D. Black
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    Ruediger.Geib@telekom.de, 
                    david.black@dell.com
        Pages:      21
        Characters: 50264
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tsvwg-diffserv-intercon-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8100

        DOI:        10.17487/RFC8100

This document defines a limited common set of Diffserv Per-Hop
Behaviors (PHBs) and Diffserv Codepoints (DSCPs) to be applied at
(inter)connections of two separately administered and operated
networks, and it explains how this approach can simplify network
configuration and operation.  Many network providers operate
Multiprotocol Label Switching (MPLS) using Treatment Aggregates for
traffic marked with different Diffserv Per-Hop Behaviors and use MPLS
for interconnection with other networks.  This document offers a
simple interconnection approach that may simplify operation of
Diffserv for network interconnection among providers that use MPLS
and apply the Short Pipe Model.  While motivated by the requirements
of MPLS network operators that use Short Pipe Model tunnels, this
document is applicable to other networks, both MPLS and non-MPLS.

This document is a product of the Transport Area Working Group Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:36:12 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC3D129495 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:12 -0700 (PDT)
X-Quarantine-ID: <5qGt42lindgQ>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5qGt42lindgQ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:11 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02CA1129482 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:36:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 532ADB8014C; Tue, 14 Mar 2017 22:35:46 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 58A07B80131; Tue, 14 Mar 2017 22:35:45 -0700 (PDT)
X-Quarantine-ID: <WMvzzAuLmNn3>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WMvzzAuLmNn3; Tue, 14 Mar 2017 22:35:41 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [196.192.112.169]) by rfc-editor.org (Postfix) with ESMTPS id 3CBFFB80134; Tue, 14 Mar 2017 22:35:41 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41326 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1b9-0002RR-NG; Wed, 15 Mar 2017 05:35:47 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5Zlsu028987; Wed, 15 Mar 2017 05:35:47 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAR7-00055w-SN for daniel@afrinic.net; Fri, 10 Mar 2017 02:37:48 +0000
Received: from mail.ietf.org ([4.31.198.44]:39284) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAR7-0005fW-8B for daniel@afrinic.net; Fri, 10 Mar 2017 02:37:45 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E6B7E1294D5; Thu,  9 Mar 2017 18:36:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489113409; bh=+P+VBB7M/lVRs29T/nxrf6+AuwxQMfzEsDQ4jPJbZec=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=SeTvc5tu07ciJnBQxhQNnf8P/DRkPZMEIpbKE4OExs1FqoiGPHEbxgTb59ee7C+JZ RDuGoDaLbBU2rQDohjz3iY9i4z5AV8sMYUTi1QyahyEHp2gy5yPM3gfWT8ec672TXI bpefhM6nfcaf4rfpGgyL2Mzyivllf6xq69P82+Kk=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52B851294CA for <ietf-announce@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2WGRqgPI4okv for <ietf-announce@ietfa.amsl.com>; Thu,  9 Mar 2017 18:36:36 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB3901294C3 for <ietf-announce@ietf.org>; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D83B6B801A3; Thu,  9 Mar 2017 18:07:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020720.D83B6B801A3@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:07:20 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RPY9dedSRDjIgWPoFdyKhu8rhUY>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8113 on Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8113

        Title:      Locator/ID Separation Protocol (LISP): Shared 
                    Extension Message & IANA Registry for 
                    Packet Type Allocations 
        Author:     M. Boucadair, C. Jacquenet
        Status:     Experimental
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mohamed.boucadair@orange.com, 
                    christian.jacquenet@orange.com
        Pages:      6
        Characters: 10608
        Updates:    RFC 6830

        I-D Tag:    draft-ietf-lisp-type-iana-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8113

        DOI:        10.17487/RFC8113

This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each
extension.  It also defines a registry for LISP Packet Type
allocations, thus updating RFC 6830.

This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:36:27 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7011129495 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:27 -0700 (PDT)
X-Quarantine-ID: <MzeLnZ-qUPM8>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MzeLnZ-qUPM8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCDD6129482 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:36:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BFAA0B80169; Tue, 14 Mar 2017 22:35:47 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 6B11EB80158; Tue, 14 Mar 2017 22:35:46 -0700 (PDT)
X-Quarantine-ID: <SvML3eDTem8R>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SvML3eDTem8R; Tue, 14 Mar 2017 22:35:42 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [196.192.112.169]) by rfc-editor.org (Postfix) with ESMTPS id 30AEAB80137; Tue, 14 Mar 2017 22:35:42 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41328 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1bA-0002Rg-MH; Wed, 15 Mar 2017 05:35:48 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5ZmEW028991; Wed, 15 Mar 2017 05:35:48 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAS3-00056B-7A for daniel@afrinic.net; Fri, 10 Mar 2017 02:38:45 +0000
Received: from mail.ietf.org ([4.31.198.44]:43043) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAS2-0005gF-Jk for daniel@afrinic.net; Fri, 10 Mar 2017 02:38:42 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B30D129507; Thu,  9 Mar 2017 18:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489113417; bh=j+gsHlNPVAwHKpsmfd3+eIWi2jFk39M22L4tZ2E7o8E=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=mZVibZZeMddHcwgMOBHrGpKaey3Uyehbzgehk+Lwzm/E0TT0j94T5bOKVAxPCtcHe R+RYsxEWlXV7TgdJSyylmjcVtihV0tWiK9T5YtxO9aGGIiis36cuZSVGrDYhlocrtj s8XJbEcUUQhJph3KiU48vLSnyQQvwsf/KjJFd4O0=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B59041294D5; Thu,  9 Mar 2017 18:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mmUA9LWGqT0e; Thu,  9 Mar 2017 18:36:37 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1E721294C4; Thu,  9 Mar 2017 18:36:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 08ED8B805C3; Thu,  9 Mar 2017 18:06:43 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020643.08ED8B805C3@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:43 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/pqHGGAz7NKclcO5kJVEpFNWwWDs>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8102 on Remote-LFA Node Protection and Manageability
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, rtgwg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8102

        Title:      Remote-LFA Node Protection and Manageability 
        Author:     P. Sarkar, Ed.,
                    S. Hegde, 
                    C. Bowers,
                    H. Gredler, 
                    S. Litkowski
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pushpasis.ietf@gmail.com, 
                    shraddha@juniper.net, 
                    cbowers@juniper.net,
                    hannes@rtbrick.com, 
                    stephane.litkowski@orange.com
        Pages:      22
        Characters: 50200
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-rlfa-node-protection-13.txt

        URL:        https://www.rfc-editor.org/info/rfc8102

        DOI:        10.17487/RFC8102

The loop-free alternates (LFAs) computed following the current
remote-LFA specification guarantees only link protection.  The
resulting remote-LFA next hops (also called "PQ-nodes") may not
guarantee node protection for all destinations being protected by it.

This document describes an extension to the remote-loop-free-based IP
fast reroute mechanisms that specifies procedures for determining
whether or not a given PQ-node provides node protection for a
specific destination.  The document also shows how the same procedure
can be utilized for the collection of complete characteristics for
alternate paths.  Knowledge about the characteristics of all
alternate paths is a precursor to applying the operator-defined
policy for eliminating paths not fitting the constraints.

This document is a product of the Routing Area Working Group Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Tue Mar 14 22:36:47 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E688129496 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:47 -0700 (PDT)
X-Quarantine-ID: <81umar9umYcn>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.092
X-Spam-Level:
X-Spam-Status: No, score=-4.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 81umar9umYcn for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 14 Mar 2017 22:36:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CF93129482 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 14 Mar 2017 22:36:45 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5A25CB8017A; Tue, 14 Mar 2017 22:35:49 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 77E69B8015E; Tue, 14 Mar 2017 22:35:47 -0700 (PDT)
X-Quarantine-ID: <MT99PJRvEkIj>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MT99PJRvEkIj; Tue, 14 Mar 2017 22:35:43 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [196.192.112.169]) by rfc-editor.org (Postfix) with ESMTPS id 34512B80138; Tue, 14 Mar 2017 22:35:43 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=41334 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1co1bB-0002Rp-Kg; Wed, 15 Mar 2017 05:35:49 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2F5Zn0Q029001; Wed, 15 Mar 2017 05:35:49 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAUy-00056m-B3 for daniel@afrinic.net; Fri, 10 Mar 2017 02:41:46 +0000
Received: from mail.ietf.org ([4.31.198.44]:45878) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1cmAUx-0005oZ-P7 for daniel@afrinic.net; Fri, 10 Mar 2017 02:41:44 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8C9129444; Thu,  9 Mar 2017 18:41:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489113699; bh=nc7izziHD2/DKTZJNpLegGgHe0r8T1GLd0qJjmMUDIc=; h=To:Subject:From:Date:Cc:Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe; b=U8q0jUozXXbw0gljR1+eiVQ7pXRhwXJDRbuGUgzMKBCBlstr38tnIpRYbVGzENx75 FHbg8KBdFOLYhOEcbxXBJXILAkJXg8WcWtjeZ/MbrNT6AxeNBop2txlhxLQJ0yauCS 5TmU30gaS6eu7Ycq+cRE30Cb2J0tWZ4LdqNVoj1Q=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFE4F1294B2; Thu,  9 Mar 2017 18:41:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EH9ZlMx3Lf6C; Thu,  9 Mar 2017 18:41:32 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F8831294E1; Thu,  9 Mar 2017 18:41:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 35E11B80184; Thu,  9 Mar 2017 18:06:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020613.35E11B80184@rfc-editor.org>
Date: Thu,  9 Mar 2017 18:06:13 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dKhqkQbJe3rMEMSPdDX39G7Ug-I>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Subject: [rfc-dist] RFC 8082 on Using Codec Control Messages in the RTP Audio-Visual Profile with Feedback with Layered Codecs
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, avtext@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8082

        Title:      Using Codec Control Messages in 
                    the RTP Audio-Visual Profile with Feedback 
                    with Layered Codecs 
        Author:     S. Wenger, J. Lennox,
                    B. Burman, M. Westerlund
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    stewe@stewe.org, 
                    jonathan@vidyo.com, 
                    bo.burman@ericsson.com,  
                    magnus.westerlund@ericsson.com
        Pages:      11
        Characters: 25093
        Updates:    RFC 5104

        I-D Tag:    draft-ietf-avtext-avpf-ccm-layered-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8082

        DOI:        10.17487/RFC8082

This document updates RFC 5104 by fixing a shortcoming in the
specification language of the Codec Control Message Full Intra
Request (FIR) description when using it with layered codecs.  In
particular, a decoder refresh point needs to be sent by a media
sender when a FIR is received on any layer of the layered bitstream,
regardless of whether those layers are being sent in a single or in
multiple RTP flows.  The other payload-specific feedback messages
defined in RFC 5104 and RFC 4585 (which was updated by RFC 5506) have
also been analyzed, and no corresponding shortcomings have been
found.

This document is a product of the Audio/Video Transport Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 17:07:57 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C96012EE45 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9NxRFi3ES7cY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:07:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC5A612ECED for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 17:07:53 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id F4058B8142F; Wed, 15 Mar 2017 17:07:40 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id A70FAB81428; Wed, 15 Mar 2017 17:07:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000739.A70FAB81428@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:39 -0700 (PDT)
Subject: [rfc-dist] RFC 8104 on Pseudowire (PW) Endpoint Fast Failure Protection
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, pals@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8104

        Title:      Pseudowire (PW) Endpoint Fast Failure 
                    Protection 
        Author:     Y. Shen, R. Aggarwal,
                    W. Henderickx, Y. Jiang
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    yshen@juniper.net, 
                    raggarwa_1@yahoo.com, 
                    wim.henderickx@nokia.com, 
                    jiangyuanlong@huawei.com
        Pages:      43
        Characters: 94878
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pals-endpoint-fast-protection-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8104

        DOI:        10.17487/RFC8104

This document specifies a fast mechanism for protecting pseudowires
(PWs) transported by IP/MPLS tunnels against egress endpoint
failures, including egress attachment circuit (AC) failure, egress
provider edge (PE) failure, multi-segment PW terminating PE failure,
and multi-segment PW switching PE failure.  Operating on the basis of
multihomed customer edge (CE), redundant PWs, upstream label
assignment, and context-specific label switching, the mechanism
enables local repair to be performed by the router upstream adjacent
to a failure.  The router can restore a PW in the order of tens of
milliseconds, by rerouting traffic around the failure to a protector
through a pre-established bypass tunnel.  Therefore, the mechanism
can be used to reduce traffic loss before global repair reacts to the
failure and the network converges on the topology changes due to the
failure.

This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 17:09:16 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17AAB1315A7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c8j7kofmlvhJ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:08 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA65312FEE1 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 17:08:11 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6A436B814E2; Wed, 15 Mar 2017 17:07:59 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 5E9CCB814DA; Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000758.5E9CCB814DA@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
Subject: [rfc-dist] BCP 209, RFC 8109 on Initializing a DNS Resolver with Priming Queries
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        BCP 209        
        RFC 8109

        Title:      Initializing a DNS Resolver with 
                    Priming Queries 
        Author:     P. Koch, M. Larson,
                    P. Hoffman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pk@DENIC.DE, 
                    matt.larson@icann.org, 
                    paul.hoffman@icann.org
        Pages:      7
        Characters: 15645
        See Also:   BCP 209

        I-D Tag:    draft-ietf-dnsop-resolver-priming-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8109

        DOI:        10.17487/RFC8109

This document describes the queries that a DNS resolver should emit
to initialize its cache.  The result is that the resolver gets both a
current NS Resource Record Set (RRset) for the root zone and the necessary address
information for reaching the root servers.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 17:09:55 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 961E1130134 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I7A5HkeIrOxp for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1657513013D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 17:08:27 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D3CD2B8153C; Wed, 15 Mar 2017 17:08:10 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id C46AFB81533; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000808.C46AFB81533@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
Subject: [rfc-dist] RFC 8119 on SIP "cause" URI Parameter for Service Number Translation
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8119

        Title:      SIP "cause" URI Parameter for 
                    Service Number Translation 
        Author:     M. Mohali, M. Barnes
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    marianne.mohali@orange.com, 
                    mary.ietf.barnes@gmail.com
        Pages:      12
        Characters: 24142
        Updates:    RFC 4458

        I-D Tag:    draft-mohali-dispatch-cause-for-service-number-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8119

        DOI:        10.17487/RFC8119

RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI
parameter, which may appear in the Request-URI of a SIP request, that
is used to indicate a reason why the request arrived to the User
Agent Server (UAS) receiving the message.  This document updates RFC
4458 by creating a new predefined value for the "cause" URI parameter
to cover service number translation for cases of retargeting due to
specific service action leading to the translation of a called
service access number.  This document also provides guidance, which
was missing in RFC 4458, for using the "cause" URI parameter within
the History-Info header field, since this use is mandatory in some IP
networks' implementations.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 23:12:11 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93AAD124D37 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:11 -0700 (PDT)
X-Quarantine-ID: <1xvouIImyYHq>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.093
X-Spam-Level:
X-Spam-Status: No, score=-4.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1xvouIImyYHq for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:10 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 624E51204DA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 23:12:10 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0FFB2B80A5B; Wed, 15 Mar 2017 23:11:57 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 27060B80A59; Wed, 15 Mar 2017 23:11:56 -0700 (PDT)
X-Quarantine-ID: <tEr6gx5rLPpw>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tEr6gx5rLPpw; Wed, 15 Mar 2017 23:11:52 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id D8658B80A58; Wed, 15 Mar 2017 23:11:51 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=39580 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1coOdX-0004Kr-3I; Thu, 16 Mar 2017 06:11:47 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2G6Bh89013440; Thu, 16 Mar 2017 06:11:43 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coJ0T-0000XC-GF for daniel@afrinic.net; Thu, 16 Mar 2017 00:11:12 +0000
Received: from mail.ietf.org ([4.31.198.44]:39578) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coJ0S-0005OQ-Sl for daniel@afrinic.net; Thu, 16 Mar 2017 00:11:05 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC17E12F257; Wed, 15 Mar 2017 17:09:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489622990; bh=oyrSdCrB+poG+DUWGC1kpfMVqngkd5t7QGFy1kWOtO0=; h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To:Cc; b=NIj6NPbjdYjG+H4Dp2VZN/4fVBg0zIkdVGpEeRZy0pXiAfllpE1djjdI56uGPr2fl wzlwoWTes+/5ZXAHACVErY+PHXJDDkmWWl18L8a/2A9BL0FOLR9hgLBAxJ9Ml9eg4r adRo6WSA5bePc6KEfqEmbFcPwI0SSUsYbWOTe4dY=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 350D61300E7 for <ietf-announce@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blXKxvGOeA_D for <ietf-announce@ietfa.amsl.com>; Wed, 15 Mar 2017 17:09:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D01513012B for <ietf-announce@ietf.org>; Wed, 15 Mar 2017 17:08:19 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C46AFB81533; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000808.C46AFB81533@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/lR4sDvs0f5NHP6OQnoVfMDxKwro>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
Subject: [rfc-dist] RFC 8119 on SIP "cause" URI Parameter for Service Number Translation
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8119

        Title:      SIP "cause" URI Parameter for 
                    Service Number Translation 
        Author:     M. Mohali, M. Barnes
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    marianne.mohali@orange.com, 
                    mary.ietf.barnes@gmail.com
        Pages:      12
        Characters: 24142
        Updates:    RFC 4458

        I-D Tag:    draft-mohali-dispatch-cause-for-service-number-14.txt

        URL:        https://www.rfc-editor.org/info/rfc8119

        DOI:        10.17487/RFC8119

RFC 4458 (regarding SIP URIs for applications) defines a "cause" URI
parameter, which may appear in the Request-URI of a SIP request, that
is used to indicate a reason why the request arrived to the User
Agent Server (UAS) receiving the message.  This document updates RFC
4458 by creating a new predefined value for the "cause" URI parameter
to cover service number translation for cases of retargeting due to
specific service action leading to the translation of a called
service access number.  This document also provides guidance, which
was missing in RFC 4458, for using the "cause" URI parameter within
the History-Info header field, since this use is mandatory in some IP
networks' implementations.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 23:12:31 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F632124D37 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:31 -0700 (PDT)
X-Quarantine-ID: <tK-n1IQZ-La2>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.093
X-Spam-Level:
X-Spam-Status: No, score=-4.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tK-n1IQZ-La2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:30 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C954E1204DA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 23:12:30 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 82348B80A63; Wed, 15 Mar 2017 23:12:02 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 4CD4AB80A59; Wed, 15 Mar 2017 23:12:01 -0700 (PDT)
X-Quarantine-ID: <eBMRE8raKzkb>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBMRE8raKzkb; Wed, 15 Mar 2017 23:11:57 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id C1FB6B80A58; Wed, 15 Mar 2017 23:11:56 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=39606 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1coOdl-0004Lg-SC; Thu, 16 Mar 2017 06:12:02 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2G6C1xG013486; Thu, 16 Mar 2017 06:12:01 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coIzY-0000Wx-LE for daniel@afrinic.net; Thu, 16 Mar 2017 00:10:15 +0000
Received: from mail.ietf.org ([4.31.198.44]:56369) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coIzY-0005Ha-1O for daniel@afrinic.net; Thu, 16 Mar 2017 00:10:08 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 809A8130A93; Wed, 15 Mar 2017 17:08:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489622937; bh=u2FRMlCQY3xUP7sbPlZpkunw62EWP6I6UVXqhw8dj2M=; h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To:Cc; b=EhYHH4qs++rjZgakktHPy6goeH/0pjQlOml7ydLuq/BznZ5tqfySlwtSvf/xuQSkb YsVxWaBfLVTgmguPkIe2CHGji4j/aLfgtU4K3diop/qr6+HsUt9MX9GLZV//K6tz7i balV//4vZdq8/BBCmtYOcrDBW9Iv+dypghvP+WVc=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5FA130153; Wed, 15 Mar 2017 17:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uiCP00hzBUUg; Wed, 15 Mar 2017 17:08:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81CA12FB9A; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E9CCB814DA; Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000758.5E9CCB814DA@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/uTXVUimkUeGJ-2xspX1769CFn18>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
Subject: [rfc-dist] BCP 209, RFC 8109 on Initializing a DNS Resolver with Priming Queries
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        BCP 209        
        RFC 8109

        Title:      Initializing a DNS Resolver with 
                    Priming Queries 
        Author:     P. Koch, M. Larson,
                    P. Hoffman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pk@DENIC.DE, 
                    matt.larson@icann.org, 
                    paul.hoffman@icann.org
        Pages:      7
        Characters: 15645
        See Also:   BCP 209

        I-D Tag:    draft-ietf-dnsop-resolver-priming-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8109

        DOI:        10.17487/RFC8109

This document describes the queries that a DNS resolver should emit
to initialize its cache.  The result is that the resolver gets both a
current NS Resource Record Set (RRset) for the root zone and the necessary address
information for reaching the root servers.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 23:12:48 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6581D124D37 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:48 -0700 (PDT)
X-Quarantine-ID: <PS5bW46U8xFL>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.093
X-Spam-Level:
X-Spam-Status: No, score=-4.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PS5bW46U8xFL for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:12:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C52CD1204DA for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 23:12:46 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id EA89AB80A67; Wed, 15 Mar 2017 23:12:04 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id C3548B80A58; Wed, 15 Mar 2017 23:12:01 -0700 (PDT)
X-Quarantine-ID: <mS6B2wI5glZ4>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mS6B2wI5glZ4; Wed, 15 Mar 2017 23:11:57 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id 7C933B80A5E; Wed, 15 Mar 2017 23:11:57 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=39598 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1coOdi-0004LP-R6; Thu, 16 Mar 2017 06:11:59 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2G6BwlB013474; Thu, 16 Mar 2017 06:11:58 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coIxo-0000WD-0k for daniel@afrinic.net; Thu, 16 Mar 2017 00:08:31 +0000
Received: from mail.ietf.org ([4.31.198.44]:50774) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <ietf-announce-bounces@ietf.org>) id 1coIxn-0005Gk-2n for daniel@afrinic.net; Thu, 16 Mar 2017 00:08:19 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AB8512F092; Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489622878; bh=cDzUdIkp6wygHPYdAOMxfUOjSoPV/nDu4DsjPFW4g+Q=; h=To:Subject:From:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To:Cc; b=h2wnYwcetG+uyJaDUJyWAiIKxoSJA8BhoYa5txuoXEU5rtLIRcNyZKirWSWL2wDXn SRpRj96z1/k4D5Qe/SGfiACbPmto59FNql1SBicVlqZ4JTZULMVL7aq3iwBpI3yiAY YOjzwLH8FmheT4u90BZ+UuiJGK6XqyP8JtFSpOuA=
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BB5112ECF5; Wed, 15 Mar 2017 17:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lmUYZMx30sCe; Wed, 15 Mar 2017 17:07:50 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 392BE12EA7A; Wed, 15 Mar 2017 17:07:50 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A70FAB81428; Wed, 15 Mar 2017 17:07:39 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000739.A70FAB81428@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:39 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dEmQvJxlfWv5fS5LjAm6uHHmmsQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
Subject: [rfc-dist] RFC 8104 on Pseudowire (PW) Endpoint Fast Failure Protection
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Reply-To: ietf@ietf.org
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org, pals@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8104

        Title:      Pseudowire (PW) Endpoint Fast Failure 
                    Protection 
        Author:     Y. Shen, R. Aggarwal,
                    W. Henderickx, Y. Jiang
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    yshen@juniper.net, 
                    raggarwa_1@yahoo.com, 
                    wim.henderickx@nokia.com, 
                    jiangyuanlong@huawei.com
        Pages:      43
        Characters: 94878
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pals-endpoint-fast-protection-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8104

        DOI:        10.17487/RFC8104

This document specifies a fast mechanism for protecting pseudowires
(PWs) transported by IP/MPLS tunnels against egress endpoint
failures, including egress attachment circuit (AC) failure, egress
provider edge (PE) failure, multi-segment PW terminating PE failure,
and multi-segment PW switching PE failure.  Operating on the basis of
multihomed customer edge (CE), redundant PWs, upstream label
assignment, and context-specific label switching, the mechanism
enables local repair to be performed by the router upstream adjacent
to a failure.  The router can restore a PW in the order of tens of
milliseconds, by rerouting traffic around the failure to a protector
through a pre-established bypass tunnel.  Therefore, the mechanism
can be used to reduce traffic loss before global repair reacts to the
failure and the network converges on the topology changes due to the
failure.

This document is a product of the Pseudowire And LDP-enabled Services Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 15 23:13:04 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79DA1124D68 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:13:04 -0700 (PDT)
X-Quarantine-ID: <JC_ZAzu15eLc>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "To"
X-Spam-Flag: NO
X-Spam-Score: -4.093
X-Spam-Level:
X-Spam-Status: No, score=-4.093 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=ietf.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JC_ZAzu15eLc for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 15 Mar 2017 23:13:03 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42B66124D37 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 15 Mar 2017 23:13:03 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5989BB80A6D; Wed, 15 Mar 2017 23:12:05 -0700 (PDT)
X-Original-To: rfc-dist+badh@rfc-editor.org
Delivered-To: rfc-dist+badh@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id A12DFB80A65; Wed, 15 Mar 2017 23:12:02 -0700 (PDT)
X-Quarantine-ID: <nSiVqgJwoe1C>
X-Virus-Scanned: amavisd-new at rfc-editor.org
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
Authentication-Results: rfcpa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ietf.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nSiVqgJwoe1C; Wed, 15 Mar 2017 23:11:58 -0700 (PDT)
Received: from smtp.mu.afrinic.net (smtp.afrinic.net [IPv6:2001:43f8:90:606::169]) by rfc-editor.org (Postfix) with ESMTPS id 771A7B80A62; Wed, 15 Mar 2017 23:11:58 -0700 (PDT)
Received: from [2001:42d0:0:410::143] (port=39604 helo=spamfilter.jnb.afrinic.net) by smtp.mu.afrinic.net with esmtps (UNKNOWN:AES256-GCM-SHA384:256) (Exim 4.72) (envelope-from <no-reply@afrinic.net>) id 1coOdk-0004LY-AR; Thu, 16 Mar 2017 06:12:01 +0000
Received: (from root@localhost) by spamfilter.jnb.afrinic.net (8.14.7/8.14.5/Submit) id v2G6BxdG013481; Thu, 16 Mar 2017 06:11:59 GMT (envelope-from no-reply@afrinic.net)
To: daniel@afrinic.net
Received: from mx02.jnb.afrinic.net ([2001:42d0:0:201::22] helo=mx.afrinic.net) by spamfilter.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <dnsop-bounces@ietf.org>) id 1coIz5-0000We-0n for daniel@afrinic.net; Thu, 16 Mar 2017 00:09:46 +0000
Received: from mail.ietf.org ([4.31.198.44]:45576) by mx.afrinic.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <dnsop-bounces@ietf.org>) id 1coIz4-0005HH-Cd for daniel@afrinic.net; Thu, 16 Mar 2017 00:09:38 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B4BF130154; Wed, 15 Mar 2017 17:08:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1489622936; bh=JlYtOq5PQnVFbhMWXK41XJ6AaVTYIbXwFHxUtbgME0E=; h=To:From:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=vcuYstYHq/DitgXIsDlcK0wNanztDr/2WDtBzXCTdvcqcPi3km/QEhO1XnTYpLBKK 9WR42jgxprys3fPY7sLsCv/UFXtl2WD0eOn/4en4rDoQE9rGXmt3jvLxSJPOpw6N91 5/IT99Jf96mt8YKMBLAsCTxTqmR+Azn43aV5jrGk=
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5FA130153; Wed, 15 Mar 2017 17:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uiCP00hzBUUg; Wed, 15 Mar 2017 17:08:53 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E81CA12FB9A; Wed, 15 Mar 2017 17:08:08 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5E9CCB814DA; Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170316000758.5E9CCB814DA@rfc-editor.org>
Date: Wed, 15 Mar 2017 17:07:58 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dnsop/XEwtPSKSJe5MLPBUeC4FqJZL9K8>
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
MIME-Version: 1.0
Subject: [rfc-dist] [DNSOP] BCP 209, RFC 8109 on Initializing a DNS Resolver with Priming Queries
X-BeenThere: rfc-dist@rfc-editor.org
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, dnsop@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        BCP 209        
        RFC 8109

        Title:      Initializing a DNS Resolver with 
                    Priming Queries 
        Author:     P. Koch, M. Larson,
                    P. Hoffman
        Status:     Best Current Practice
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pk@DENIC.DE, 
                    matt.larson@icann.org, 
                    paul.hoffman@icann.org
        Pages:      7
        Characters: 15645
        See Also:   BCP 209

        I-D Tag:    draft-ietf-dnsop-resolver-priming-11.txt

        URL:        https://www.rfc-editor.org/info/rfc8109

        DOI:        10.17487/RFC8109

This document describes the queries that a DNS resolver should emit
to initialize its cache.  The result is that the resolver gets both a
current NS Resource Record Set (RRset) for the root zone and the necessary address
information for reaching the root servers.

This document is a product of the Domain Name System Operations Working Group of the IETF.


BCP: This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for 
improvements. Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
DNSOP mailing list
DNSOP@ietf.org
https://www.ietf.org/mailman/listinfo/dnsop
_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:09:58 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47A5A12965D for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DnkptM_-pbMw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:09:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2FDE12965B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:09:56 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 987C8B80D88; Fri, 17 Mar 2017 16:09:41 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 07876B80D87; Fri, 17 Mar 2017 16:09:40 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317230940.07876B80D87@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:09:40 -0700 (PDT)
Subject: [rfc-dist] RFC 8029 on Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8029

        Title:      Detecting Multiprotocol Label Switched (MPLS) 
                    Data-Plane Failures 
        Author:     K. Kompella, 
                    G. Swallow,
                    C. Pignataro, Ed.,
                    N. Kumar, 
                    S. Aldrin,
                    M. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    kireeti.kompella@gmail.com, 
                    swallow.ietf@gmail.com, 
                    cpignata@cisco.com, 
                    naikumar@cisco.com, 
                    aldrin.ietf@gmail.com,
                    mach.chen@huawei.com
        Pages:      78
        Characters: 174158
        Obsoletes:  RFC 4379, RFC 6424, RFC 6829, RFC 7537
        Updates:    RFC 1122

        I-D Tag:    draft-ietf-mpls-rfc4379bis-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8029

        DOI:        10.17487/RFC8029

This document describes a simple and efficient mechanism to detect
data-plane failures in Multiprotocol Label Switching (MPLS) Label
Switched Paths (LSPs).  It defines a probe message called an "MPLS                       
echo request" and a response message called an "MPLS echo reply" for
returning the result of the probe.  The MPLS echo request is intended
to contain sufficient information to check correct operation of the
data plane and to verify the data plane against the control plane,
thereby localizing faults.

This document obsoletes RFCs 4379, 6424, 6829, and 7537, and updates
RFC 1122.

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:10:38 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA4212967A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zQaCg-QY_V7Y for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:10:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02DFD129677 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:10:20 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 288F1B80D94; Fri, 17 Mar 2017 16:10:07 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 18BD3B80D93; Fri, 17 Mar 2017 16:10:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317231004.18BD3B80D93@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:10:04 -0700 (PDT)
Subject: [rfc-dist] RFC 8106 on IPv6 Router Advertisement Options for DNS Configuration
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, ipv6@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8106

        Title:      IPv6 Router Advertisement Options for 
                    DNS Configuration 
        Author:     J. Jeong, 
                    S. Park,
                    L. Beloeil, 
                    S. Madanapalli
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    pauljeong@skku.edu, 
                    soohong.park@samsung.com, 
                    luc.beloeil@orange.com, 
                    smadanapalli@gmail.com
        Pages:      19
        Characters: 43092
        Obsoletes:  RFC 6106

        I-D Tag:    draft-ietf-6man-rdnss-rfc6106bis-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8106

        DOI:        10.17487/RFC8106

This document specifies IPv6 Router Advertisement (RA) options
(called "DNS RA options") to allow IPv6 routers to advertise a list
of DNS Recursive Server Addresses and a DNS Search List to IPv6
hosts.

This document, which obsoletes RFC 6106, defines a higher default
value of the lifetime of the DNS RA options to reduce the likelihood
of expiry of the options on links with a relatively high rate of
packet loss.

This document is a product of the IPv6 Maintenance Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:11:01 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD80812967E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I3nP-PeVAZVL for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:00 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7561712965D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:10:40 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 9C344B80DA2; Fri, 17 Mar 2017 16:10:27 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 8FF5AB80DA1; Fri, 17 Mar 2017 16:10:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317231026.8FF5AB80DA1@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:10:26 -0700 (PDT)
Subject: [rfc-dist] RFC 8114 on Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast Network
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: softwires@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8114

        Title:      Delivery of IPv4 Multicast Services 
                    to IPv4 Clients over an IPv6 
                    Multicast Network 
        Author:     M. Boucadair,
                    C. Qin,
                    C. Jacquenet, 
                    Y. Lee,
                    Q. Wang
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mohamed.boucadair@orange.com, 
                    jacni@jacni.com, 
                    christian.jacquenet@orange.com,  
                    yiu_lee@cable.comcast.com, 
                    13301168516@189.cn
        Pages:      23
        Characters: 47896
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-dslite-multicast-18.txt

        URL:        https://www.rfc-editor.org/info/rfc8114

        DOI:        10.17487/RFC8114

This document specifies a solution for the delivery of IPv4 multicast
services to IPv4 clients over an IPv6 multicast network.  The
solution relies upon a stateless IPv4-in-IPv6 encapsulation scheme
and uses an IPv6 multicast distribution tree to deliver IPv4
multicast traffic.  The solution is particularly useful for the
delivery of multicast service offerings to customers serviced by
Dual-Stack Lite (DS-Lite).

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:11:29 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AED2129687 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsZJb8f1VZ4t for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45608129689 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:10:57 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 0F3E9B80DAA; Fri, 17 Mar 2017 16:10:44 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 29B59B80DA9; Fri, 17 Mar 2017 16:10:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317231042.29B59B80DA9@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:10:42 -0700 (PDT)
Subject: [rfc-dist] RFC 8115 on DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 Prefixes
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: softwires@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8115

        Title:      DHCPv6 Option for IPv4-Embedded Multicast 
                    and Unicast IPv6 Prefixes 
        Author:     M. Boucadair, 
                    J. Qin,
                    T. Tsou, 
                    X. Deng
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mohamed.boucadair@orange.com, 
                    jacni@jacni.com, 
                    tina.tsou@philips.com,
                    dxhbupt@gmail.com
        Pages:      9
        Characters: 17386
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-softwire-multicast-prefix-option-15.txt

        URL:        https://www.rfc-editor.org/info/rfc8115

        DOI:        10.17487/RFC8115

This document defines a Dynamic Host Configuration Protocol version 6
(DHCPv6) Option for multicast IPv4 service continuity solutions,
which is used to carry the IPv6 prefixes to be used to build unicast
and multicast IPv4-embedded IPv6 addresses.

This document is a product of the Softwires Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:11:57 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB31129677 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WnsG4PaMe2xB for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:11:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEE0B12952D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:11:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 74A16B80DBE; Fri, 17 Mar 2017 16:11:02 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 981F6B80DBC; Fri, 17 Mar 2017 16:11:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317231101.981F6B80DBC@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:11:01 -0700 (PDT)
Subject: [rfc-dist] RFC 8118 on The application/pdf Media Type
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8118

        Title:      The application/pdf Media Type 
        Author:     M. Hardy,
                    L. Masinter,
                    D. Markovic, 
                    D. Johnson,
                    M. Bailey
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    mahardy@adobe.com, 
                    masinter@adobe.com, 
                    dmarkovi@adobe.com, 
                    duff.johnson@pdfa.org, 
                    martin.bailey@globalgraphics.com
        Pages:      12
        Characters: 24463
        Obsoletes:  RFC 3778

        I-D Tag:    draft-hardy-pdf-mime-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8118

        DOI:        10.17487/RFC8118

The Portable Document Format (PDF) is an ISO standard (ISO
32000-1:2008) defining a final-form document representation language
in use for document exchange, including on the Internet, since 1993.
This document provides an overview of the PDF format and updates the
media type registration of "application/pdf".  It obsoletes RFC 3778.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Fri Mar 17 16:12:19 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44A1F1296BC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:12:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V0R4bEgTwu7A for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 17 Mar 2017 16:12:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DA1412969B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 17 Mar 2017 16:11:31 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D79B2B80DC6; Fri, 17 Mar 2017 16:11:13 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id C2BD9B80DC7; Fri, 17 Mar 2017 16:11:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170317231112.C2BD9B80DC7@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:11:12 -0700 (PDT)
Subject: [rfc-dist] RFC 8122 on Connection-Oriented Media Transport over the Transport Layer Security (TLS) Protocol in the Session Description Protocol (SDP)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, mmusic@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8122

        Title:      Connection-Oriented Media Transport over the 
                    Transport Layer Security (TLS) Protocol in 
                    the Session Description Protocol (SDP) 
        Author:     J. Lennox, 
                    C. Holmberg
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    jonathan@vidyo.com, 
                    christer.holmberg@ericsson.com
        Pages:      18
        Characters: 42792
        Obsoletes:  RFC 4572

        I-D Tag:    draft-ietf-mmusic-4572-update-13.txt

        URL:        https://www.rfc-editor.org/info/rfc8122

        DOI:        10.17487/RFC8122

This document specifies how to establish secure connection-oriented
media transport sessions over the Transport Layer Security (TLS)
protocol using the Session Description Protocol (SDP).  It defines
the SDP protocol identifier, 'TCP/TLS'.  It also defines the syntax
and semantics for an SDP 'fingerprint' attribute that identifies the
certificate that will be presented for the TLS session.  This
mechanism allows media transport over TLS connections to be
established securely, so long as the integrity of session
descriptions is assured.

This document obsoletes RFC 4572 by clarifying the usage of multiple
fingerprints.

This document is a product of the Multiparty Multimedia Session Control Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 22 15:56:17 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F1CB126C83 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:56:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7buSaHThpzHm for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:56:15 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1F5C127058 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Mar 2017 15:56:15 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 781E9B80D77; Wed, 22 Mar 2017 15:56:09 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 2A536B80D76; Wed, 22 Mar 2017 15:56:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170322225609.2A536B80D76@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:56:09 -0700 (PDT)
Subject: [rfc-dist] RFC 8076 on A Usage for Shared Resources in RELOAD (ShaRe)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, p2psip@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8076

        Title:      A Usage for Shared Resources 
                    in RELOAD (ShaRe) 
        Author:     A. Knauf, 
                    T. Schmidt, Ed.,
                    G. Hege,
                    M. Waehlisch
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    alexanderknauf@gmail.com, 
                    t.schmidt@haw-hamburg.de, 
                    hege@daviko.com,  
                    mw@link-lab.net
        Pages:      22
        Characters: 46545
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-p2psip-share-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8076

        DOI:        10.17487/RFC8076

This document defines a REsource LOcation And Discovery (RELOAD)
Usage for managing shared write access to RELOAD Resources.  Shared
Resources in RELOAD (ShaRe) form a basic primitive for enabling
various coordination and notification schemes among distributed
peers.  Access in ShaRe is controlled by a hierarchical trust
delegation scheme maintained within an access list.  A new
USER-CHAIN-ACL access policy allows authorized peers to write a Shared
Resource without owning its corresponding certificate.  This
specification also adds mechanisms to store Resources with a variable
name that is useful whenever peer-independent rendezvous processes
are required.

This document is a product of the Peer-to-Peer Session Initiation Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 22 15:56:54 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AE79129B60 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:56:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id APpUWUSpV7s1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:56:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DEFF129ACC for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Mar 2017 15:56:36 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id E40FEB80D7F; Wed, 22 Mar 2017 15:56:30 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 8F782B80D84; Wed, 22 Mar 2017 15:56:29 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170322225629.8F782B80D84@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:56:29 -0700 (PDT)
Subject: [rfc-dist] RFC 8101 on IANA Registration of New Session Initiation Protocol (SIP) Resource-Priority Namespace for Mission Critical Push To Talk Service
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8101

        Title:      IANA Registration of New Session 
                    Initiation Protocol (SIP) Resource-Priority Namespace for 
                    Mission Critical Push To Talk Service 
        Author:     C. Holmberg,  
                    J. Axell
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    christer.holmberg@ericsson.com, 
                    jorgen.axell@ericsson.com
        Pages:      6
        Characters: 10649
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-holmberg-dispatch-mcptt-rp-namespace-05.txt

        URL:        https://www.rfc-editor.org/info/rfc8101

        DOI:        10.17487/RFC8101

This document creates additional Session Initiation Protocol (SIP)
Resource-Priority namespaces to meet the requirements of the
3GPP-defined Mission Critical Push To Talk (MCPTT) and places these
namespaces in the corresponding IANA registry.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 22 15:57:14 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28885129C26 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QxfBLlS-fsNC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:12 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70F98129B3A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Mar 2017 15:56:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 56E9FB80D95; Wed, 22 Mar 2017 15:56:47 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 2FB6FB80D93; Wed, 22 Mar 2017 15:56:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170322225646.2FB6FB80D93@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:56:46 -0700 (PDT)
Subject: [rfc-dist] RFC 8123 on Requirements for Marking SIP Messages to be Logged
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, insipid@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8123

        Title:      Requirements for Marking SIP Messages 
                    to be Logged 
        Author:     P. Dawes, 
                    C. Arunachalam
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    peter.dawes@vodafone.com, 
                    carunach@cisco.com
        Pages:      11
        Characters: 22368
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-insipid-logme-reqs-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8123

        DOI:        10.17487/RFC8123

SIP networks use signaling monitoring tools to debug customer-
reported problems and for regression testing if network or client
software is upgraded.  As networks grow and become interconnected,
including connection via transit networks, it becomes impractical to
predict the path that SIP signaling will take between clients and,
therefore, impractical to monitor SIP signaling end-to-end.

This document describes the requirements for adding an indicator to
the SIP Protocol Data Unit (PDU) or a SIP message that marks the PDU
as a candidate for logging.  Such a marking will typically be applied
as part of network testing controlled by the network operator and not
used in regular client signaling.  However, such a marking can be
carried end-to-end, including the SIP terminals, even if a session
originates and terminates in different networks.

This document is a product of the INtermediary-safe SIP session ID Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 22 15:57:44 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DEBE129C30 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sHmcXRGY91AE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:36 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866561299F3 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Mar 2017 15:57:07 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B902CB80D9C; Wed, 22 Mar 2017 15:57:00 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 7410DB80DA0; Wed, 22 Mar 2017 15:56:59 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170322225659.7410DB80DA0@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:56:59 -0700 (PDT)
Subject: [rfc-dist] RFC 8129 on Authentication Indicator in Kerberos Tickets
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: kitten@ietf.org, drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8129

        Title:      Authentication Indicator in Kerberos Tickets 
        Author:     A. Jain, 
                    N. Kinder,
                    N. McCallum
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    ajain323@gatech.edu, 
                    nkinder@redhat.com, 
                    npmccallum@redhat.com
        Pages:      6
        Characters: 11296
        Updates:    RFC 4120

        I-D Tag:    draft-ietf-kitten-krb-auth-indicator-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8129

        DOI:        10.17487/RFC8129

This document updates RFC 4120, as it specifies an extension in the
Kerberos protocol.  It defines a new authorization data type,
AD-AUTHENTICATION-INDICATOR.  The purpose of introducing this data
type is to include an indicator of the strength of a client's
authentication in service tickets so that application services can
use it as an input into policy decisions.

This document is a product of the Common Authentication Technology Next Generation Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 22 15:57:57 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36B8C129C4E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OlOjFMahQh7x for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 22 Mar 2017 15:57:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6788129512 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 22 Mar 2017 15:57:23 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1E68FB80DB2; Wed, 22 Mar 2017 15:57:13 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id C4FC0B80DAD; Wed, 22 Mar 2017 15:57:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170322225711.C4FC0B80DAD@rfc-editor.org>
Date: Wed, 22 Mar 2017 15:57:11 -0700 (PDT)
Subject: [rfc-dist] RFC 8131 on RSVP-TE Signaling Procedure for End-to-End GMPLS Restoration and Resource Sharing
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, teas@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8131

        Title:      RSVP-TE Signaling Procedure for End-to-End 
                    GMPLS Restoration and Resource Sharing 
        Author:     X. Zhang, 
                    H. Zheng, Ed.,
                    R. Gandhi, Ed.,
                    Z. Ali,
                    P. Brzozowski
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    zhang.xian@huawei.com, 
                    zhenghaomian@huawei.com, 
                    rgandhi@cisco.com,  
                    zali@cisco.com, 
                    pbrzozowski@advaoptical.com
        Pages:      15
        Characters: 33403
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-teas-gmpls-resource-sharing-proc-08.txt

        URL:        https://www.rfc-editor.org/info/rfc8131

        DOI:        10.17487/RFC8131

In non-packet transport networks, there are requirements where
the Generalized Multiprotocol Label Switching (GMPLS) end-to-end
recovery scheme needs to employ a restoration Label Switched Path (LSP)
while keeping resources for the working and/or protecting LSPs
reserved in the network after the failure occurs.

This document reviews how the LSP association is to be provided using
Resource Reservation Protocol - Traffic Engineering (RSVP-TE)
signaling in the context of a GMPLS end-to-end recovery scheme when
using restoration LSP where failed LSP is not torn down.  In
addition, this document discusses resource sharing-based setup and
teardown of LSPs as well as LSP reversion procedures.  No new
signaling extensions are defined by this document, and it is strictly
informative in nature.

This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Wed Mar 29 14:20:57 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE201298CC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 29 Mar 2017 14:20:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WYJ1AXZl4-_3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 29 Mar 2017 14:20:56 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD5F41288B8 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 29 Mar 2017 14:20:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C6EA3B80EA0; Wed, 29 Mar 2017 14:20:39 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 63942B80E9F; Wed, 29 Mar 2017 14:20:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170329212038.63942B80E9F@rfc-editor.org>
Date: Wed, 29 Mar 2017 14:20:38 -0700 (PDT)
Subject: [rfc-dist] RFC 8073 on Coordinating Attack Response at Internet Scale (CARIS) Workshop Report
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8073

        Title:      Coordinating Attack Response at Internet 
                    Scale (CARIS) Workshop Report 
        Author:     K. Moriarty, M. Ford
        Status:     Informational
        Stream:     IAB
        Date:       March 2017
        Mailbox:    Kathleen.Moriarty@dell.com, 
                    ford@isoc.org
        Pages:      16
        Characters: 36872
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-carisreport-02.txt

        URL:        https://www.rfc-editor.org/info/rfc8073

        DOI:        10.17487/RFC8073

This report documents the discussions and conclusions from the
Coordinating Attack Response at Internet Scale (CARIS) workshop that
took place in Berlin, Germany on 18 June 2015.  The purpose of this
workshop was to improve mutual awareness, understanding, and
coordination among the diverse participating organizations and their
representatives.

Note that this document is a report on the proceedings of the
workshop.  The views and positions documented in this report are
those of the workshop participants and do not necessarily reflect IAB
views and positions.

This document is a product of the Internet Architecture Board.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar 30 14:39:56 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A59591296B5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VftAeC9fB6Uy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:39:54 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBC2A127B31 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 30 Mar 2017 14:39:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 01A2DB80E4A; Thu, 30 Mar 2017 14:39:39 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id EB12DB80E49; Thu, 30 Mar 2017 14:39:37 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170330213937.EB12DB80E49@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:39:37 -0700 (PDT)
Subject: [rfc-dist] RFC 8110 on Opportunistic Wireless Encryption
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8110

        Title:      Opportunistic Wireless Encryption 
        Author:     D. Harkins, Ed.,
                    W. Kumari, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       March 2017
        Mailbox:    dharkins@arubanetworks.com, 
                    warren@kumari.net
        Pages:      12
        Characters: 26719
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-harkins-owe-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8110

        DOI:        10.17487/RFC8110

This memo specifies an extension to IEEE Std 802.11 to provide for
opportunistic (unauthenticated) encryption to the wireless media.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar 30 14:40:18 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA1851296D4 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9kHzRtVY4y50 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:40:17 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECCD2127B31 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 30 Mar 2017 14:40:12 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 677D9B80E53; Thu, 30 Mar 2017 14:39:55 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id D0A95B80E52; Thu, 30 Mar 2017 14:39:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170330213954.D0A95B80E52@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:39:54 -0700 (PDT)
Subject: [rfc-dist] RFC 8124 on The Session Description Protocol (SDP) WebSocket Connection URI Attribute
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, bfcpbis@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8124

        Title:      The Session Description Protocol (SDP) 
                    WebSocket Connection URI Attribute 
        Author:     R. Ravindranath, 
                    G. Salgueiro
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    rmohanr@cisco.com, 
                    gsalguei@cisco.com
        Pages:      12
        Characters: 24562
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-bfcpbis-sdp-ws-uri-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8124

        DOI:        10.17487/RFC8124

The WebSocket protocol enables bidirectional real-time communication
between clients and servers in web-based applications.  This document
specifies extensions to Session Description Protocol (SDP) for
application protocols using WebSocket as a transport.

This document is a product of the Binary Floor Control Protocol Bis Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar 30 14:40:49 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BA71296FA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hM7zXPDrv6IM for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:40:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 901CD12963F for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 30 Mar 2017 14:40:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C3049B80E5C; Thu, 30 Mar 2017 14:40:09 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 6D845B80E5A; Thu, 30 Mar 2017 14:40:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170330214008.6D845B80E5A@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:40:08 -0700 (PDT)
Subject: [rfc-dist] RFC 8130 on RTP Payload Format for the Mixed Excitation Linear Prediction Enhanced (MELPe) Codec
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, payload@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8130

        Title:      RTP Payload Format for the 
                    Mixed Excitation Linear Prediction Enhanced (MELPe) 
                    Codec 
        Author:     V. Demjanenko, D. Satterlee
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    victor.demjanenko@vocal.com, 
                    david.satterlee@vocal.com
        Pages:      30
        Characters: 64594
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-payload-melpe-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8130

        DOI:        10.17487/RFC8130

This document describes the RTP payload format for the Mixed
Excitation Linear Prediction Enhanced (MELPe) speech coder.  MELPe's
three different speech encoding rates and sample frame sizes are
supported.  Comfort noise procedures and packet loss concealment are
described in detail.

This document is a product of the Audio/Video Transport Payloads Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org

From rfc-dist-bounces@rfc-editor.org  Thu Mar 30 14:41:16 2017
Return-Path: <rfc-dist-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-dist-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A950129736 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bR2po4P_eiPF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 30 Mar 2017 14:41:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AEA71296F2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 30 Mar 2017 14:40:47 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3435BB80E65; Thu, 30 Mar 2017 14:40:24 -0700 (PDT)
X-Original-To: rfc-dist@rfc-editor.org
Delivered-To: rfc-dist@rfc-editor.org
Received: by rfc-editor.org (Postfix, from userid 30) id 51FBCB80E63; Thu, 30 Mar 2017 14:40:22 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170330214022.51FBCB80E63@rfc-editor.org>
Date: Thu, 30 Mar 2017 14:40:22 -0700 (PDT)
Subject: [rfc-dist] RFC 8133 on The Security Evaluated Standardized Password-Authenticated Key Exchange (SESPAKE) Protocol
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8133

        Title:      The Security Evaluated Standardized 
                    Password-Authenticated 
                    Key Exchange (SESPAKE) Protocol 
        Author:     S. Smyshlyaev. Ed., 
                    E. Alekseev,
                    I. Oshkin, 
                    V. Popov
        Status:     Informational
        Stream:     Independent
        Date:       March 2017
        Mailbox:    svs@cryptopro.ru, 
                    alekseev@cryptopro.ru, 
                    oshkin@cryptopro.ru,  
                    vpopov@cryptopro.ru
        Pages:      51
        Characters: 89986
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-smyshlyaev-sespake-16.txt

        URL:        https://www.rfc-editor.org/info/rfc8133

        DOI:        10.17487/RFC8133

This document describes the Security Evaluated Standardized Password-
Authenticated Key Exchange (SESPAKE) protocol.  The SESPAKE protocol
provides password-authenticated key exchange for usage in systems for
protection of sensitive information.  The security proofs of the
protocol were made for situations involving an active adversary in
the channel, including man-in-the-middle (MitM) attacks and attacks
based on the impersonation of one of the subjects.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
rfc-dist mailing list
rfc-dist@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-dist
http://www.rfc-editor.org
