
From rfc-dist-bounces@rfc-editor.org  Mon Sep 19 14:35:05 2016
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 0DC9012B549 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 PDoCXlTHZG0C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35: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 C7B4A12B006 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Sep 2016 14:35:03 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id A0009B81182; Mon, 19 Sep 2016 14:35: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 EFBCCB8117F; Mon, 19 Sep 2016 14:35:00 -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: <20160919213500.EFBCCB8117F@rfc-editor.org>
Date: Mon, 19 Sep 2016 14:35:00 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7943 on A Method for Generating Semantically Opaque Interface Identifiers (IIDs) with the Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7943

        Title:      A Method for Generating Semantically 
                    Opaque Interface Identifiers (IIDs) with the 
                    Dynamic Host Configuration Protocol for IPv6 
                    (DHCPv6) 
        Author:     F. Gont, W. Liu
        Status:     Informational
        Stream:     Independent
        Date:       September 2016
        Mailbox:    fgont@si6networks.com, 
                    liushucheng@huawei.com
        Pages:      10
        Characters: 21161
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-gont-dhcpv6-stable-privacy-addresses-02.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7943

This document describes a method for selecting IPv6 Interface
Identifiers that can be employed by Dynamic Host Configuration
Protocol for IPv6 (DHCPv6) servers when leasing non-temporary IPv6
addresses to DHCPv6 clients.  This method is a DHCPv6 server-side
algorithm that does not require any updates to the existing DHCPv6
specifications.  The aforementioned method results in stable
addresses within each subnet, even in the presence of multiple DHCPv6
servers or DHCPv6 server reinstallments.  It is a DHCPv6 variant of
the method specified in RFC 7217 for IPv6 Stateless Address
Autoconfiguration.


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  Mon Sep 19 14:35:44 2016
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 6629812B552 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 nFIk1VysSuOX for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Mon, 19 Sep 2016 14:35: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 756BB12B554 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Mon, 19 Sep 2016 14:35:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 523D2B8118F; Mon, 19 Sep 2016 14:35:28 -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 00799B8118D; Mon, 19 Sep 2016 14:35: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: <20160919213527.00799B8118D@rfc-editor.org>
Date: Mon, 19 Sep 2016 14:35:26 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7976 on Updates to Private Header (P-Header) Extension Usage in Session Initiation Protocol (SIP) Requests and Responses
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7976

        Title:      Updates to Private Header (P-Header) 
                    Extension Usage in Session Initiation Protocol 
                    (SIP) Requests and Responses 
        Author:     C. Holmberg, N. Biondic, G. Salgueiro
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    christer.holmberg@ericsson.com, 
                    nevenka.biondic@ericsson.com, 
                    gsalguei@cisco.com
        Pages:      8
        Characters: 17246
        Updates:    RFC 7315

        I-D Tag:    draft-holmberg-dispatch-rfc7315-updates-09.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7976

The Third Generation Partnership Project (3GPP) has identified cases
where different SIP private header extensions referred to as "P-"
header fields, and defined in RFC 7315, need to be included in SIP
requests and responses currently not allowed according to RFC 7315.
This document updates RFC 7315, in order to allow inclusion of the
affected "P-" header fields in such requests and responses.

This document also makes updates for RFC 7315 in order to fix
misalignments that occurred when RFC 3455 was updated and obsoleted
by RFC 7315.


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 Sep 21 16:16:30 2016
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 C4BBC12BBE2 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:16:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 rC34O4GtBTKC for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:16:29 -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 2C32412BC30 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Sep 2016 16:16:29 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2B357B80FB8; Wed, 21 Sep 2016 16:16:28 -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 A8D4CB80FB6; Wed, 21 Sep 2016 16:16:27 -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: <20160921231627.A8D4CB80FB6@rfc-editor.org>
Date: Wed, 21 Sep 2016 16:16:27 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7954 on Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7954

        Title:      Locator/ID Separation Protocol (LISP) Endpoint 
                    Identifier (EID) Block 
        Author:     L. Iannone, D. Lewis,
                    D. Meyer, V. Fuller
        Status:     Experimental
        Stream:     IETF
        Date:       September 2016
        Mailbox:    ggx@gigix.net, 
                    darlewis@cisco.com, 
                    dmm@1-4-5.net,  vaf@vaf.net
        Pages:      12
        Characters: 26522
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lisp-eid-block-13.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7954

This document directs IANA to allocate a /32 IPv6 prefix for use with
the Locator/ID Separation Protocol (LISP).  The prefix will be used
for local intra-domain routing and global endpoint identification, by
sites deploying LISP as Endpoint Identifier (EID) addressing space.

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  Wed Sep 21 16:17:10 2016
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 8485412C042 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 wBDqAypF-PkU for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:04 -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 67BDD12C083 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Sep 2016 16:16:50 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id CB051B80FD0; Wed, 21 Sep 2016 16:16:49 -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 23432B80FCF; Wed, 21 Sep 2016 16:16:48 -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: <20160921231648.23432B80FCF@rfc-editor.org>
Date: Wed, 21 Sep 2016 16:16:48 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7955 on Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7955

        Title:      Management Guidelines for the Locator/ID 
                    Separation Protocol (LISP) Endpoint Identifier (EID) 
                    Block 
        Author:     L. Iannone, R. Jorgensen,
                    D. Conrad, G. Huston
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    ggx@gigix.net, 
                    rogerj@gmail.com, 
                    drc@virtualized.org, 
                    gih@apnic.net
        Pages:      10
        Characters: 19607
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lisp-eid-block-mgmnt-07.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7955

This document proposes a framework for the management of the Locator/
ID Separation Protocol (LISP) Endpoint Identifier (EID) address
block.  The framework described relies on hierarchical distribution
of the address space, granting temporary usage of prefixes of such
space to requesting organizations.

This document is a product of the Locator/ID Separation Protocol 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 Sep 21 16:17:42 2016
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 EDDC012D1EA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 w9z27KB0pmvT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:41 -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 9A5AB12D186 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Sep 2016 16:17:05 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 743FCB80FDD; Wed, 21 Sep 2016 16:16: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 B6381B80FDE; Wed, 21 Sep 2016 16:16: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: <20160921231658.B6381B80FDE@rfc-editor.org>
Date: Wed, 21 Sep 2016 16:16:58 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7977 on The WebSocket Protocol as a Transport for the Message Session Relay Protocol (MSRP)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7977

        Title:      The WebSocket Protocol as a 
                    Transport for the Message Session Relay 
                    Protocol (MSRP) 
        Author:     P. Dunkley, G. Llewellyn,
                    V. Pascual, G. Salgueiro,
                    R. Ravindranath
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    peter.dunkley@xura.com, 
                    gavin.llewellyn@xura.com, 
                    victor.pascual.avila@oracle.com,
                    gsalguei@cisco.com, 
                    rmohanr@cisco.com
        Pages:      28
        Characters: 52078
        Updates:    RFC 4975, RFC 4976

        I-D Tag:    draft-pd-dispatch-msrp-websocket-15.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7977

The WebSocket protocol enables two-way real-time communication
between clients and servers in situations where direct access to TCP
and UDP is not available (for example, from within JavaScript in a
web browser).  This document specifies a new WebSocket subprotocol as
a reliable transport mechanism between Message Session Relay Protocol
(MSRP) clients and relays to enable usage of MSRP in new scenarios.
This document normatively updates RFCs 4975 and 4976.

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 Sep 21 22:00:53 2016
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 8C3C912BFC8 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 22:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 hOqUHWDVm-HQ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 21 Sep 2016 22:00: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 2E95512BFEF for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 21 Sep 2016 22:00:52 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D1EF3B80C47; Wed, 21 Sep 2016 22:00:50 -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 BFFBBB80C3E; Wed, 21 Sep 2016 22:00:41 -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: <20160922050041.BFFBBB80C3E@rfc-editor.org>
Date: Wed, 21 Sep 2016 22:00:41 -0700 (PDT)
Cc: drafts-update-ref@iana.org, tram@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7982 on Measurement of Round-Trip Time and Fractional Loss Using Session Traversal Utilities for NAT (STUN)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7982

        Title:      Measurement of Round-Trip Time and 
                    Fractional Loss Using Session Traversal Utilities 
                    for NAT (STUN) 
        Author:     P. Martinsen, 
                    T. Reddy,
                    D. Wing, 
                    V. Singh
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    palmarti@cisco.com, 
                    tireddy@cisco.com, 
                    dwing-ietf@fuggles.com,  
                    varun@callstats.io
        Pages:      10
        Characters: 19893
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-tram-stun-path-data-05.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7982

A host with multiple interfaces needs to choose the best interface for
communication.  Oftentimes, this decision is based on a static
configuration and does not consider the path characteristics, which
may affect the user experience.

This document describes a mechanism for an endpoint to measure the
path characteristics fractional loss and RTT using Session Traversal
Utilities for NAT (STUN) messages.

This document is a product of the TURN Revised and Modernized 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 Sep 22 16:14:13 2016
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 9CC9012B5B6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Sep 2016 16:14:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 46AT_9FB7LPL for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 22 Sep 2016 16:14: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 6326B12B4CD for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 22 Sep 2016 16:14:12 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 65DE4B80F12; Thu, 22 Sep 2016 16:14:11 -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 457B2B80F10; Thu, 22 Sep 2016 16:14:10 -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: <20160922231410.457B2B80F10@rfc-editor.org>
Date: Thu, 22 Sep 2016 16:14:10 -0700 (PDT)
Cc: drafts-update-ref@iana.org, icnrg@irtf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7945 on Information-Centric Networking: Evaluation and Security Considerations
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7945

        Title:      Information-Centric Networking: Evaluation and 
                    Security Considerations 
        Author:     K. Pentikousis, Ed.,
                    B. Ohlman, 
                    E. Davies,
                    S. Spirou, 
                    G. Boggia
        Status:     Informational
        Stream:     IRTF
        Date:       September 2016
        Mailbox:    k.pentikousis@travelping.com, 
                    Borje.Ohlman@ericsson.com, 
                    davieseb@scss.tcd.ie,  
                    spis@intracom-telecom.com, 
                    g.boggia@poliba.it
        Pages:      38
        Characters: 95970
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-icnrg-evaluation-methodology-05.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7945

This document presents a number of considerations regarding evaluating
Information-Centric Networking (ICN) and sheds some light on the
impact of ICN on network security.  It also surveys the evaluation
tools currently available to researchers in the ICN area and provides
suggestions regarding methodology and metrics.


This document is a product of the Information-Centric Networking Research 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 Sep 23 23:04:46 2016
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 612C812B9BD for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Sep 2016 23:04:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 5mN_X8KBMQz9 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 23 Sep 2016 23:04: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 AAF8A12B7F2 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 23 Sep 2016 23:04:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B3A89B81121; Fri, 23 Sep 2016 23:04:43 -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 C6F41B81120; Fri, 23 Sep 2016 23:04: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: <20160924060442.C6F41B81120@rfc-editor.org>
Date: Fri, 23 Sep 2016 23:04:42 -0700 (PDT)
Cc: drafts-update-ref@iana.org, dime@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7966 on Security at the Attribute-Value Pair (AVP) Level for Non-neighboring Diameter Nodes: Scenarios and Requirements
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7966

        Title:      Security at the Attribute-Value Pair (AVP)
                    Level for Non-neighboring Diameter Nodes: 
                    Scenarios and Requirements 
        Author:     H. Tschofenig, 
                    J. Korhonen, Ed., 
                    G. Zorn,
                    K. Pillay
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    Hannes.tschofenig@gmx.net, 
                    jouni.nospam@gmail.com, 
                    glenzorn@gmail.com,  
                    kervin.pillay@gmail.com
        Pages:      11
        Characters: 22186
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dime-e2e-sec-req-05.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7966

This specification specifies requirements for providing Diameter
security at the level of individual Attribute-Value Pairs (AVPs).

This document is a product of the Diameter Maintenance and Extensions 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 Sep 29 16:40:09 2016
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 5AE0F12B0A5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 IpZT6AVZiMxz for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:40:06 -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 D724812B09C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 29 Sep 2016 16:40:06 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C4918B810FA; Thu, 29 Sep 2016 16:40:05 -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 2066BB810F9; Thu, 29 Sep 2016 16:40: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: <20160929234004.2066BB810F9@rfc-editor.org>
Date: Thu, 29 Sep 2016 16:40:04 -0700 (PDT)
Cc: drafts-update-ref@iana.org, dmarc@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7960 on Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7960

        Title:      Interoperability Issues between Domain-based Message 
                    Authentication, Reporting, and Conformance (DMARC) and 
                    Indirect Email Flows 
        Author:     F. Martin, Ed.,
                    E. Lear, Ed.,
                    T. Draegen. Ed.,
                    E. Zwicky, Ed., 
                    K. Andersen, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       September 2016
        Mailbox:    fmartin@linkedin.com, 
                    lear@cisco.com, 
                    tim@dmarcian.com,
                    zwicky@yahoo-inc.com, 
                    kandersen@linkedin.com
        Pages:      27
        Characters: 58739
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dmarc-interoperability-18.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7960

Domain-based Message Authentication, Reporting, and Conformance
(DMARC) introduces a mechanism for expressing domain-level policies
and preferences for email message validation, disposition, and
reporting.  However, the DMARC mechanism enables potentially
disruptive interoperability issues when messages do not flow directly
from the author's administrative domain to the final Recipients.
Collectively, these email flows are referred to as "indirect email
flows".  This document describes these interoperability issues and
presents possible methods for addressing them.

This document is a product of the Domain-based Message Authentication, Reporting & Conformance 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 Sep 29 16:40:40 2016
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 BA50C12B364 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 3Nqo6nr3wkRd for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:40:38 -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 36DB112B33D for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 29 Sep 2016 16:40:28 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 5BAC3B81106; Thu, 29 Sep 2016 16:40: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 54D4DB81104; Thu, 29 Sep 2016 16:40: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: <20160929234026.54D4DB81104@rfc-editor.org>
Date: Thu, 29 Sep 2016 16:40:26 -0700 (PDT)
Cc: drafts-update-ref@iana.org, idr@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7964 on Solutions for BGP Persistent Route Oscillation
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7964

        Title:      Solutions for BGP Persistent Route 
                    Oscillation 
        Author:     D. Walton, A. Retana,
                    E. Chen, J. Scudder
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    dwalton@cumulusnetworks.com, 
                    aretana@cisco.com, 
                    enkechen@cisco.com,
                    jgs@juniper.net
        Pages:      9
        Characters: 19774
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-idr-route-oscillation-stop-04.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7964

Routing information reduction by BGP Route Reflection or
Confederation can result in persistent internal BGP route
oscillations with certain routing setups and network topologies.
This document specifies two sets of additional paths that can be used
to eliminate these route oscillations in a network.

This document is a product of the 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  Thu Sep 29 16:41:21 2016
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 3265612B39C for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:41:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 Blb3heUq3FHw for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:41:19 -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 26B0A12B37A for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 29 Sep 2016 16:40:44 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 1043BB8110E; Thu, 29 Sep 2016 16:40:43 -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 C84C0B81109; Thu, 29 Sep 2016 16:40:41 -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: <20160929234041.C84C0B81109@rfc-editor.org>
Date: Thu, 29 Sep 2016 16:40:41 -0700 (PDT)
Cc: drafts-update-ref@iana.org, avt@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7983 on Multiplexing Scheme Updates for Secure Real-time Transport Protocol (SRTP) Extension for Datagram Transport Layer Security (DTLS)
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7983

        Title:      Multiplexing Scheme Updates for Secure 
                    Real-time Transport Protocol (SRTP) Extension for 
                    Datagram Transport Layer Security (DTLS) 
        Author:     M. Petit-Huguenin, G. Salgueiro
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    marc@petit-huguenin.org, 
                    gsalguei@cisco.com
        Pages:      13
        Characters: 24894
        Updates:    RFC 5764

        I-D Tag:    draft-ietf-avtcore-rfc5764-mux-fixes-11.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7983

This document defines how Datagram Transport Layer Security (DTLS),
Real-time Transport Protocol (RTP), RTP Control Protocol (RTCP),
Session Traversal Utilities for NAT (STUN), Traversal Using Relays
around NAT (TURN), and ZRTP packets are multiplexed on a single
receiving socket.  It overrides the guidance from RFC 5764 ("SRTP
Extension for DTLS"), which suffered from four issues described and
fixed in this document.

This document updates RFC 5764.

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  Thu Sep 29 16:41:52 2016
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 5D2AA12B436 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 dX_prJ4gJC_V for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu, 29 Sep 2016 16:41: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 763B512B382 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu, 29 Sep 2016 16:41:04 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id C838EB8111D; Thu, 29 Sep 2016 16:41:03 -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 04EF5B8111C; Thu, 29 Sep 2016 16:41:02 -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: <20160929234102.04EF5B8111C@rfc-editor.org>
Date: Thu, 29 Sep 2016 16:41:02 -0700 (PDT)
Cc: drafts-update-ref@iana.org, sipcore@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7984 on Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7984

        Title:      Locating Session Initiation Protocol (SIP) 
                    Servers in a Dual-Stack IP Network 
        Author:     O. Johansson, G. Salgueiro,
                    V. Gurbani, D. Worley, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    oej@edvina.net, 
                    gsalguei@cisco.com, 
                    vkg@bell-labs.com, 
                    worley@ariadne.com
        Pages:      10
        Characters: 21246
        Updates:    RFC 3263

        I-D Tag:    draft-ietf-sipcore-dns-dual-stack-08.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7984

RFC 3263 defines how a Session Initiation Protocol (SIP)
implementation, given a SIP Uniform Resource Identifier (URI), should
locate the next-hop SIP server using Domain Name System (DNS)
procedures.  As SIP networks increasingly transition from IPv4-only
to dual-stack, a quality user experience must be ensured for dual-
stack SIP implementations.  This document updates the DNS procedures
described in RFC 3263 for dual-stack SIP implementations in
preparation for forthcoming specifications for applying "Happy
Eyeballs" principles to SIP.

This document is a product of the Session Initiation Protocol Core 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 Sep 30 14:37:42 2016
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 C9BC712B1F3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Sep 2016 14:37:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 aBAR28rzX_e6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Sep 2016 14:37:40 -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 1E651128B44 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 30 Sep 2016 14:37:40 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 31FE2B80342; Fri, 30 Sep 2016 14:37: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 D0D94B8033F; Fri, 30 Sep 2016 14:37: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: <20160930213737.D0D94B8033F@rfc-editor.org>
Date: Fri, 30 Sep 2016 14:37:37 -0700 (PDT)
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7903 on Windows Image Media Types
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7903

        Title:      Windows Image Media Types 
        Author:     S. Leonard
        Status:     Informational
        Stream:     Independent
        Date:       September 2016
        Mailbox:    dev+ietf@seantek.com
        Pages:      12
        Characters: 24094
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-seantek-windows-image-03.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7903

This document registers media types for certain image formats
promulgated in Microsoft Windows, namely image/wmf, image/x-wmf,
image/emf, image/x-emf, and image/bmp for use with Windows Metafile,
Enhanced Metafile, and Windows Bitmap formats.  Originally designed
for Microsoft Windows 2.0 and 3.0, these image files are intended to
be portable between applications and devices, and they may contain both
vector and raster graphics.


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 Sep 30 14:38:22 2016
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 A33B612B1E1 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Sep 2016 14:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 28XNPkhYdfGh for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 30 Sep 2016 14:38:21 -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 17BAA12B009 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 30 Sep 2016 14:38:21 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D1C24B803D3; Fri, 30 Sep 2016 14:38:20 -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 C10EAB803D2; Fri, 30 Sep 2016 14:38:19 -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: <20160930213819.C10EAB803D2@rfc-editor.org>
Date: Fri, 30 Sep 2016 14:38:19 -0700 (PDT)
Cc: drafts-update-ref@iana.org, trill@ietf.org, rfc-editor@rfc-editor.org
Subject: [rfc-dist] RFC 7978 on Transparent Interconnection of Lots of Links (TRILL): RBridge Channel Header Extension
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.15
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>
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 7978

        Title:      Transparent Interconnection of Lots of 
                    Links (TRILL): RBridge Channel Header Extension 
        Author:     D. Eastlake 3rd, M. Umair, Y. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2016
        Mailbox:    d3e3e3@gmail.com, 
                    mohammed.umair2@gmail.com, 
                    liyizhou@huawei.com
        Pages:      25
        Characters: 54617
        Updates:    RFC 7178

        I-D Tag:    draft-ietf-trill-channel-tunnel-11.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7978

The IETF TRILL (Transparent Interconnection of Lots of Links) protocol
includes an optional mechanism (specified in RFC 7178) called RBridge
Channel for the transmission of typed messages between TRILL switches
in the same campus and the transmission of such messages between TRILL
switches and end stations on the same link.  This document specifies
extensions to the RBridge Channel protocol header to support two
features as follows: (1) a standard method to tunnel payloads whose
type can be indicated by Ethertype through encapsulation in RBridge
Channel messages; and (2) a method to support security facilities for
RBridge Channel messages.  This document updates RFC 7178.

This document is a product of the Transparent Interconnection of Lots of Links 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
