
From rfc-dist-bounces@rfc-editor.org  Thu Feb  6 13:02:26 2020
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 8415312082F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  6 Feb 2020 13:02:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 zTvPpeonn5GT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  6 Feb 2020 13:02:24 -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 7A9BE1200E5 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  6 Feb 2020 13:02:24 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id AB609F406CC; Thu,  6 Feb 2020 13:02:07 -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 5D06AF406CC; Thu,  6 Feb 2020 13:02:06 -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: <20200206210206.5D06AF406CC@rfc-editor.org>
Date: Thu,  6 Feb 2020 13:02:06 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8698_on_Network-Assisted_Dynamic_Adapta?= =?utf-8?q?tion_=28NADA=29=3A_A_Unified_Congestion_Control_Scheme_for_Real?= =?utf-8?q?-Time_Media?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, rmcat@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 8698

        Title:      Network-Assisted Dynamic Adaptation (NADA): A 
                    Unified Congestion Control Scheme for Real-Time 
                    Media 
        Author:     X. Zhu, 
                    R. Pan,
                    M. Ramalho,
                    S. Mena
        Status:     Experimental
        Stream:     IETF
        Date:       February 2020
        Mailbox:    xiaoqzhu@cisco.com, 
                    rong.pan@intel.com, 
                    mar42@cornell.edu,
                    semena@cisco.com
        Pages:      26
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmcat-nada-13.txt

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

        DOI:        10.17487/RFC8698

This document describes Network-Assisted Dynamic Adaptation (NADA), a
novel congestion control scheme for interactive real-time media
applications such as video conferencing. In the proposed scheme, the
sender regulates its sending rate, based on either implicit or
explicit congestion signaling, in a unified approach. The scheme can
benefit from Explicit Congestion Notification (ECN) markings from
network nodes. It also maintains consistent sender behavior in the
absence of such markings by reacting to queuing delays and packet
losses instead.

This document is a product of the RTP Media Congestion Avoidance Techniques 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 Feb  6 14:07:10 2020
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 8ED74120863 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  6 Feb 2020 14:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 7tLHJHLMKpO5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Thu,  6 Feb 2020 14:07:08 -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 12FA212011B for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Thu,  6 Feb 2020 14:07:08 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 26AE0F406F5; Thu,  6 Feb 2020 14:06:51 -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 74774F406F0; Thu,  6 Feb 2020 14:06:49 -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: <20200206220649.74774F406F0@rfc-editor.org>
Date: Thu,  6 Feb 2020 14:06:49 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8686_on_Application-Layer_Traffic_Optim?= =?utf-8?q?ization_=28ALTO=29_Cross=E2=80=91Domain_Server_Discovery?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, alto@ietf.org, rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-dist-bounces@rfc-editor.org
Sender: "rfc-dist" <rfc-dist-bounces@rfc-editor.org>

QSBuZXcgUmVxdWVzdCBmb3IgQ29tbWVudHMgaXMgbm93IGF2YWlsYWJsZSBpbiBvbmxpbmUgUkZD
IGxpYnJhcmllcy4KCiAgICAgICAgCiAgICAgICAgUkZDIDg2ODYKCiAgICAgICAgVGl0bGU6ICAg
ICAgQXBwbGljYXRpb24tTGF5ZXIgVHJhZmZpYyBPcHRpbWl6YXRpb24gKEFMVE8pIAogICAgICAg
ICAgICAgICAgICAgIENyb3Nz4oCRRG9tYWluIFNlcnZlciBEaXNjb3ZlcnkgCiAgICAgICAgQXV0
aG9yOiAgICAgUy4gS2llc2VsLAogICAgICAgICAgICAgICAgICAgIE0uIFN0aWVtZXJsaW5nCiAg
ICAgICAgU3RhdHVzOiAgICAgU3RhbmRhcmRzIFRyYWNrCiAgICAgICAgU3RyZWFtOiAgICAgSUVU
RgogICAgICAgIERhdGU6ICAgICAgIEZlYnJ1YXJ5IDIwMjAKICAgICAgICBNYWlsYm94OiAgICBp
ZXRmLWFsdG9Ac2tpZXNlbC5kZSwgCiAgICAgICAgICAgICAgICAgICAgbWxzLmlldGZAZ21haWwu
Y29tCiAgICAgICAgUGFnZXM6ICAgICAgMzQKICAgICAgICBVcGRhdGVzL09ic29sZXRlcy9TZWVB
bHNvOiAgIE5vbmUKCiAgICAgICAgSS1EIFRhZzogICAgZHJhZnQtaWV0Zi1hbHRvLXhkb20tZGlz
Yy0wNi50eHQKCiAgICAgICAgVVJMOiAgICAgICAgaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
aW5mby9yZmM4Njg2CgogICAgICAgIERPSTogICAgICAgIDEwLjE3NDg3L1JGQzg2ODYKClRoZSBn
b2FsIG9mIEFwcGxpY2F0aW9uLUxheWVyIFRyYWZmaWMgT3B0aW1pemF0aW9uIChBTFRPKSBpcyB0
bwpwcm92aWRlIGd1aWRhbmNlIHRvIGFwcGxpY2F0aW9ucyB0aGF0IGhhdmUgdG8gc2VsZWN0IG9u
ZSBvciBzZXZlcmFsCmhvc3RzIGZyb20gYSBzZXQgb2YgY2FuZGlkYXRlcyBjYXBhYmxlIG9mIHBy
b3ZpZGluZyBhIGRlc2lyZWQKcmVzb3VyY2UuICBBTFRPIGlzIHJlYWxpemVkIGJ5IGEgY2xpZW50
LXNlcnZlciBwcm90b2NvbC4gIEJlZm9yZSBhbgpBTFRPIGNsaWVudCBjYW4gYXNrIGZvciBndWlk
YW5jZSwgaXQgbmVlZHMgdG8gZGlzY292ZXIgb25lIG9yIG1vcmUKQUxUTyBzZXJ2ZXJzIHRoYXQg
Y2FuIHByb3ZpZGUgc3VpdGFibGUgZ3VpZGFuY2UuCgpJbiBzb21lIGRlcGxveW1lbnQgc2NlbmFy
aW9zLCBpbiBwYXJ0aWN1bGFyIGlmIHRoZSBpbmZvcm1hdGlvbiBhYm91dAp0aGUgbmV0d29yayB0
b3BvbG9neSBpcyBwYXJ0aXRpb25lZCBhbmQgZGlzdHJpYnV0ZWQgb3ZlciBzZXZlcmFsIEFMVE8K
c2VydmVycywgaXQgbWF5IGJlIG5lY2Vzc2FyeSB0byBkaXNjb3ZlciBhbiBBTFRPIHNlcnZlciBv
dXRzaWRlIG9mCnRoZSBBTFRPIGNsaWVudCdzIG93biBuZXR3b3JrIGRvbWFpbiwgaW4gb3JkZXIg
dG8gZ2V0IGFwcHJvcHJpYXRlCmd1aWRhbmNlLiAgVGhpcyBkb2N1bWVudCBkZXRhaWxzIGFwcGxp
Y2FibGUgc2NlbmFyaW9zLCBpdGVtaXplcwpyZXF1aXJlbWVudHMsIGFuZCBzcGVjaWZpZXMgYSBw
cm9jZWR1cmUgZm9yIEFMVE8gY3Jvc3MtZG9tYWluIHNlcnZlcgpkaXNjb3ZlcnkuCgpUZWNobmlj
YWxseSwgdGhlIHByb2NlZHVyZSBzcGVjaWZpZWQgaW4gdGhpcyBkb2N1bWVudCB0YWtlcyBvbmUK
SVDCoGFkZHJlc3Mgb3IgcHJlZml4IGFuZCBhIFUtTkFQVFIgU2VydmljZSBQYXJhbWV0ZXIgKHR5
cGljYWxseSwKIkFMVE86aHR0cHMiKSBhcyBwYXJhbWV0ZXJzLiBJdCBwZXJmb3JtcyBETlMgbG9v
a3VwcyAoZm9yIE5BUFRSCnJlc291cmNlIHJlY29yZHMgaW4gdGhlICJpbi1hZGRyLmFycGEuIiBv
ciAiaXA2LmFycGEuIiB0cmVlcykgYW5kCnJldHVybnMgb25lIG9yIG1vcmUgVVJJcyBvZiBpbmZv
cm1hdGlvbiByZXNvdXJjZXMgcmVsYXRlZCB0byB0aGF0IElQCmFkZHJlc3Mgb3IgcHJlZml4LgoK
VGhpcyBkb2N1bWVudCBpcyBhIHByb2R1Y3Qgb2YgdGhlIEFwcGxpY2F0aW9uLUxheWVyIFRyYWZm
aWMgT3B0aW1pemF0aW9uIFdvcmtpbmcgR3JvdXAgb2YgdGhlIElFVEYuCgpUaGlzIGlzIG5vdyBh
IFByb3Bvc2VkIFN0YW5kYXJkLgoKU1RBTkRBUkRTIFRSQUNLOiBUaGlzIGRvY3VtZW50IHNwZWNp
ZmllcyBhbiBJbnRlcm5ldCBTdGFuZGFyZHMgVHJhY2sKcHJvdG9jb2wgZm9yIHRoZSBJbnRlcm5l
dCBjb21tdW5pdHksIGFuZCByZXF1ZXN0cyBkaXNjdXNzaW9uIGFuZCBzdWdnZXN0aW9ucwpmb3Ig
aW1wcm92ZW1lbnRzLiAgUGxlYXNlIHJlZmVyIHRvIHRoZSBjdXJyZW50IGVkaXRpb24gb2YgdGhl
IE9mZmljaWFsCkludGVybmV0IFByb3RvY29sIFN0YW5kYXJkcyAoaHR0cHM6Ly93d3cucmZjLWVk
aXRvci5vcmcvc3RhbmRhcmRzKSBmb3IgdGhlIApzdGFuZGFyZGl6YXRpb24gc3RhdGUgYW5kIHN0
YXR1cyBvZiB0aGlzIHByb3RvY29sLiAgRGlzdHJpYnV0aW9uIG9mIHRoaXMgCm1lbW8gaXMgdW5s
aW1pdGVkLgoKVGhpcyBhbm5vdW5jZW1lbnQgaXMgc2VudCB0byB0aGUgSUVURi1Bbm5vdW5jZSBh
bmQgcmZjLWRpc3QgbGlzdHMuClRvIHN1YnNjcmliZSBvciB1bnN1YnNjcmliZSwgc2VlCiAgaHR0
cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9pZXRmLWFubm91bmNlCiAgaHR0cHM6
Ly9tYWlsbWFuLnJmYy1lZGl0b3Iub3JnL21haWxtYW4vbGlzdGluZm8vcmZjLWRpc3QKCkZvciBz
ZWFyY2hpbmcgdGhlIFJGQyBzZXJpZXMsIHNlZSBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9yZy9z
ZWFyY2gKRm9yIGRvd25sb2FkaW5nIFJGQ3MsIHNlZSBodHRwczovL3d3dy5yZmMtZWRpdG9yLm9y
Zy9yZXRyaWV2ZS9idWxrCgpSZXF1ZXN0cyBmb3Igc3BlY2lhbCBkaXN0cmlidXRpb24gc2hvdWxk
IGJlIGFkZHJlc3NlZCB0byBlaXRoZXIgdGhlCmF1dGhvciBvZiB0aGUgUkZDIGluIHF1ZXN0aW9u
LCBvciB0byByZmMtZWRpdG9yQHJmYy1lZGl0b3Iub3JnLiAgVW5sZXNzCnNwZWNpZmljYWxseSBu
b3RlZCBvdGhlcndpc2Ugb24gdGhlIFJGQyBpdHNlbGYsIGFsbCBSRkNzIGFyZSBmb3IKdW5saW1p
dGVkIGRpc3RyaWJ1dGlvbi4KCgpUaGUgUkZDIEVkaXRvciBUZWFtCkFzc29jaWF0aW9uIE1hbmFn
ZW1lbnQgU29sdXRpb25zLCBMTEMKCgpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXwpyZmMtZGlzdCBtYWlsaW5nIGxpc3QKcmZjLWRpc3RAcmZjLWVkaXRvci5v
cmcKaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvbWFpbG1hbi9saXN0aW5mby9yZmMtZGlzdApo
dHRwOi8vd3d3LnJmYy1lZGl0b3Iub3JnCg==

From rfc-dist-bounces@rfc-editor.org  Fri Feb  7 10:02:22 2020
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 97264120947 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  7 Feb 2020 10:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 Hsxnf9Se8GnE for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri,  7 Feb 2020 10:02: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 7060B12093C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri,  7 Feb 2020 10:02:21 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 77714F406F0; Fri,  7 Feb 2020 10:02:03 -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 779AFF406DA; Fri,  7 Feb 2020 10:02:02 -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: <20200207180202.779AFF406DA@rfc-editor.org>
Date: Fri,  7 Feb 2020 10:02:02 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?BCP_84=2C_RFC_8704_on_Enhanced_Feasible-Pat?= =?utf-8?q?h_Unicast_Reverse_Path_Forwarding?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, opsec@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 84        
        RFC 8704

        Title:      Enhanced Feasible-Path Unicast Reverse Path 
                    Forwarding 
        Author:     K. Sriram,
                    D. Montgomery,
                    J. Haas
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    ksriram@nist.gov, 
                    dougm@nist.gov, 
                    jhaas@juniper.net
        Pages:      17
        Updates:    RFC 3704
        See Also:   BCP 84

        I-D Tag:    draft-ietf-opsec-urpf-improvements-04.txt

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

        DOI:        10.17487/RFC8704

This document identifies a need for and proposes improvement of the
unicast Reverse Path Forwarding (uRPF) techniques (see RFC 3704) for
detection and mitigation of source address spoofing (see BCP 38).
Strict uRPF is inflexible about directionality, the loose uRPF is
oblivious to directionality, and the current feasible-path uRPF
attempts to strike a balance between the two (see RFC 3704). However,
as shown in this document, the existing feasible-path uRPF still has
shortcomings. This document describes enhanced feasible-path uRPF
(EFP-uRPF) techniques that are more flexible (in a meaningful way)
about directionality than the feasible-path uRPF (RFC 3704). The
proposed EFP-uRPF methods aim to significantly reduce false positives
regarding invalid detection in source address validation (SAV).
Hence, they can potentially alleviate ISPs' concerns about the
possibility of disrupting service for their customers and encourage
greater deployment of uRPF techniques. This document updates RFC
3704.

This document is a product of the Operational Security Capabilities for IP Network Infrastructure 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 Feb 11 21:37:05 2020
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 401D212083B for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 11 Feb 2020 21:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 Qpvfz-hv285E for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Tue, 11 Feb 2020 21:37:03 -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 5B0AB120863 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Tue, 11 Feb 2020 21:37:03 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 2CD80F40709; Tue, 11 Feb 2020 21:36: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 A35E9F406F7; Tue, 11 Feb 2020 21:36: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: <20200212053637.A35E9F406F7@rfc-editor.org>
Date: Tue, 11 Feb 2020 21:36:37 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8703_on_Dynamic_Link_Exchange_Protocol_?= =?utf-8?q?=28DLEP=29_Link_Identifier_Extension?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, manet@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 8703

        Title:      Dynamic Link Exchange Protocol (DLEP) 
                    Link Identifier Extension 
        Author:     R. Taylor,
                    S. Ratliff
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    rick.taylor@airbus.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-manet-dlep-lid-extension-06.txt

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

        DOI:        10.17487/RFC8703

The Dynamic Link Exchange Protocol (DLEP) is a protocol for modems to
advertise the status of wireless links between reachable destinations
to attached routers. The core specification of the protocol (RFC
8175) assumes that every modem in the radio network has an attached
DLEP router and requires that the Media Access Control (MAC) address
of the DLEP interface on the attached router be used to identify the
destination in the network, for purposes of reporting the state and
quality of the link to that destination.  

This document describes a DLEP extension that allows modems that do
not meet the strict requirement above to use DLEP to describe link
availability and quality to one or more destinations reachable beyond
a device on the Layer 2 domain.

This document is a product of the Mobile Ad-hoc Networks 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 Feb 12 11:03:27 2020
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 55B12120AA3 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 Uv42LXM6GHYY for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:25 -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 33DBD120AA7 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Feb 2020 11:03:25 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 80225F40714; Wed, 12 Feb 2020 11:03:00 -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 177D3F40714; Wed, 12 Feb 2020 11:02: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: <20200212190259.177D3F40714@rfc-editor.org>
Date: Wed, 12 Feb 2020 11:02:59 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_4405_on_SMTP_Servi?= =?utf-8?q?ce_Extension_for_Indicating_the_Responsible_Submitter_of_an_E-M?= =?utf-8?q?ail_Message?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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: 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>

RFC 4405 has been reclassified as Historic.
        
        RFC 4405

        Title:      SMTP Service Extension for Indicating 
                    the Responsible Submitter of an E-Mail 
                    Message 
        Author:     E. Allman,
                    H. Katz
        Status:     Historic
        Stream:     IETF
        Date:       April 2006
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-katz-submitter-01.txt

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

        DOI:        10.17487/RFC4405

This memo defines an extension to the Simple Mail Transfer Protocol
(SMTP) service that allows an SMTP client to specify the
responsible submitter of an e-mail message.  The responsible
submitter is the e-mail address of the entity most recently
responsible for introducing a message into the transport stream.
This extension helps receiving e-mail servers efficiently determine
whether the SMTP client is authorized to transmit mail on behalf of
the responsible submitter's domain.  This memo defines an Experimental Protocol for the Internet community.


HISTORIC: This memo defines a Historic Document 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 Feb 12 11:03:45 2020
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 57A9A120AD6 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 9QmDVuD0IdhB for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:03:44 -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 33221120B04 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Feb 2020 11:03:44 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id BEFAEF40725; Wed, 12 Feb 2020 11:03:06 -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 6199BF40724; Wed, 12 Feb 2020 11:03:05 -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: <20200212190305.6199BF40724@rfc-editor.org>
Date: Wed, 12 Feb 2020 11:03:05 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_4406_on_Sender_ID?= =?utf-8?q?=3A_Authenticating_E-Mail?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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: 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>

RFC 4406 has been reclassified as Historic.
        
        RFC 4406

        Title:      Sender ID: Authenticating E-Mail 
        Author:     J. Lyon,
                    M. Wong
        Status:     Historic
        Stream:     IETF
        Date:       April 2006
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-lyon-senderid-core-01.txt

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

        DOI:        10.17487/RFC4406

Internet mail suffers from the fact that much unwanted mail is sent
using spoofed addresses -- "spoofed" in this case means that the address
is used without the permission of the domain owner.  This document
describes a family of tests by which SMTP servers can determine
whether an e-mail address in a received message was used with the
permission of the owner of the domain contained in that e-mail
address.  This memo defines an Experimental Protocol for the Internet community.


HISTORIC: This memo defines a Historic Document 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 Feb 12 11:04:11 2020
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 28320120BCA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 h6zarZMR6DUy for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 11:04:09 -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 2103A120B4E for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Feb 2020 11:04:04 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 07FCAF4073A; Wed, 12 Feb 2020 11:03: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 76355F40739; Wed, 12 Feb 2020 11:03: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: <20200212190313.76355F40739@rfc-editor.org>
Date: Wed, 12 Feb 2020 11:03:13 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?Moved_to_Historic=3A_RFC_4407_on_Purported_?= =?utf-8?q?Responsible_Address_in_E-Mail_Messages?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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: 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>

RFC 4407 has been reclassified as Historic.
        
        RFC 4407

        Title:      Purported Responsible Address in E-Mail 
                    Messages 
        Author:     J. Lyon
        Status:     Historic
        Stream:     IETF
        Date:       April 2006
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-lyon-senderid-pra-01.txt

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

        DOI:        10.17487/RFC4407

This document defines an algorithm by which, given an e-mail message,
one can extract the identity of the party that appears to have most
proximately caused that message to be delivered.  This identity is
called the Purported Responsible Address (PRA).This memo defines an Experimental Protocol for the Internet community.  


HISTORIC: This memo defines a Historic Document 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 Feb 12 15:12:31 2020
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 E2BBC120013 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 15:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 raDLrP1bMXAx for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 12 Feb 2020 15:12:30 -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 EB4ED12001E for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 12 Feb 2020 15:12:30 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 037D9F40723; Wed, 12 Feb 2020 15:12:06 -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 90CEAF40721; Wed, 12 Feb 2020 15:12: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: <20200212231204.90CEAF40721@rfc-editor.org>
Date: Wed, 12 Feb 2020 15:12:04 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8708_on_Use_of_the_HSS/LMS_Hash-Based_S?= =?utf-8?q?ignature_Algorithm_in_the_Cryptographic_Message_Syntax_=28CMS?= =?utf-8?q?=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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: spasm@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 8708

        Title:      Use of the HSS/LMS Hash-Based Signature Algorithm 
                    in the Cryptographic Message Syntax (CMS) 
        Author:     R. Housley
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    housley@vigilsec.com
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lamps-cms-hash-sig-10.txt

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

        DOI:        10.17487/RFC8708

This document specifies the conventions for using the Hierarchical
Signature System (HSS) / Leighton-Micali Signature (LMS) hash-based
signature algorithm with the Cryptographic Message Syntax (CMS).  In
addition, the algorithm identifier and public key syntax are
provided.  The HSS/LMS algorithm is one form of hash-based digital
signature; it is described in RFC 8554.

This document is a product of the Limited Additional Mechanisms for PKIX and SMIME 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 Feb 19 14:57:13 2020
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 37FA01200C7 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 19 Feb 2020 14:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 RSz-6xZmBMNA for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 19 Feb 2020 14:57:11 -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 D7166120821 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 19 Feb 2020 14:57:11 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 29217F40714; Wed, 19 Feb 2020 14:57:07 -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 E7187F40713; Wed, 19 Feb 2020 14:57:05 -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: <20200219225705.E7187F40713@rfc-editor.org>
Date: Wed, 19 Feb 2020 14:57:05 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?BCP_225=2C_RFC_8725_on_JSON_Web_Token_Best_?= =?utf-8?q?Current_Practices?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, oauth@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 225        
        RFC 8725

        Title:      JSON Web Token Best Current Practices 
        Author:     Y. Sheffer,
                    D. Hardt,
                    M. Jones
        Status:     Best Current Practice
        Stream:     IETF
        Date:       February 2020
        Mailbox:    yaronf.ietf@gmail.com, 
                    dick.hardt@gmail.com, 
                    mbj@microsoft.com
        Pages:      13
        Updates:    RFC 7519
        See Also:   BCP 225

        I-D Tag:    draft-ietf-oauth-jwt-bcp-07.txt

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

        DOI:        10.17487/RFC8725

JSON Web Tokens, also known as JWTs, are URL-safe JSON-based security
tokens that contain a set of claims that can be signed and/or
encrypted. JWTs are being widely used and deployed as a simple
security token format in numerous protocols and applications, both in
the area of digital identity and in other application areas.  This
Best Current Practices document updates RFC 7519 to provide
actionable guidance leading to secure implementation and deployment
of JWTs.

This document is a product of the Web Authorization Protocol 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 Feb 19 14:57:30 2020
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 8083F120960 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 19 Feb 2020 14:57:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 pX0TpTDdEZqF for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Wed, 19 Feb 2020 14:57:29 -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 15A0412087C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Wed, 19 Feb 2020 14:57:29 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 6974BF4072C; Wed, 19 Feb 2020 14:57: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 33AA0F40738; Wed, 19 Feb 2020 14:57: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: <20200219225713.33AA0F40738@rfc-editor.org>
Date: Wed, 19 Feb 2020 14:57:13 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8742_on_Concise_Binary_Object_Represent?= =?utf-8?q?ation_=28CBOR=29_Sequences?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, cbor@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 8742

        Title:      Concise Binary Object Representation (CBOR) 
                    Sequences 
        Author:     C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    cabo@tzi.org
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-cbor-sequence-02.txt

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

        DOI:        10.17487/RFC8742

This document describes the Concise Binary Object Representation
(CBOR) Sequence format and associated media type
"application/cbor-seq".  A CBOR Sequence consists of any number of
encoded CBOR data items, simply concatenated in sequence.

Structured syntax suffixes for media types allow other media types to
build on them and make it explicit that they are built on an existing
media type as their foundation.  This specification defines and
registers "+cbor-seq" as a structured syntax suffix for CBOR
Sequences.

This document is a product of the Concise Binary Object Representation Maintenance and 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 Feb 21 14:33:45 2020
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 DCE041200E5 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 14:33:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 PnTSMHTcqwLT for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 14:33:44 -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 AE68C1200C3 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Feb 2020 14:33:44 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 74622F4071A; Fri, 21 Feb 2020 14:33:37 -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 507A5F40719; Fri, 21 Feb 2020 14:33:36 -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: <20200221223336.507A5F40719@rfc-editor.org>
Date: Fri, 21 Feb 2020 14:33:36 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8695_on_A_YANG_Data_Model_for_the_Routi?= =?utf-8?q?ng_Information_Protocol_=28RIP=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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 8695

        Title:      A YANG Data Model for 
                    the Routing Information Protocol (RIP) 
        Author:     X. Liu,
                    P. Sarda,
                    V. Choudhary
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    xufeng.liu.ietf@gmail.com, 
                    prateek.sarda@ericsson.com, 
                    vikschw@gmail.com
        Pages:      40
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtgwg-yang-rip-11.txt

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

        DOI:        10.17487/RFC8695

This document describes a data model for the management of the
Routing Information Protocol (RIP).  Both RIP version 2 and RIPng are
covered.  The data model includes definitions for configuration,
operational state, and Remote Procedure Calls (RPCs).

The YANG data model in this document conforms to the Network
Management Datastore Architecture (NMDA).

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  Fri Feb 21 14:36:13 2020
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 38E9612008F for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 14:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.2
X-Spam-Level:
X-Spam-Status: No, score=-5.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 eM_Uo1kxLtlQ for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 14:36:12 -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 1F6221200DB for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Feb 2020 14:36:12 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D44DCF4071A; Fri, 21 Feb 2020 14:36:04 -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 BEA98F40719; Fri, 21 Feb 2020 14:36:03 -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: <20200221223603.BEA98F40719@rfc-editor.org>
Date: Fri, 21 Feb 2020 14:36:03 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8734_on_Elliptic_Curve_Cryptography_=28?= =?utf-8?q?ECC=29_Brainpool_Curves_for_Transport_Layer_Security_=28TLS=29_?= =?utf-8?q?Version_1=2E3?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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 8734

        Title:      Elliptic Curve Cryptography (ECC) Brainpool 
                    Curves for Transport Layer Security (TLS) 
                    Version 1.3 
        Author:     L. Bruckert,
                    J. Merkle,
                    M. Lochter
        Status:     Informational
        Stream:     Independent
        Date:       February 2020
        Mailbox:    leonie.bruckert@secunet.com, 
                    johannes.merkle@secunet.com, 
                    manfred.lochter@bsi.bund.de
        Pages:      11
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-bruckert-brainpool-for-tls13-07.txt

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

        DOI:        10.17487/RFC8734

Elliptic Curve Cryptography (ECC) Brainpool curves were an option for
authentication and key exchange in the Transport Layer Security (TLS)
protocol version 1.2 but were deprecated by the IETF for use with TLS
version 1.3 because they had little usage. However, these curves have
not been shown to have significant cryptographical weaknesses, and
there is some interest in using several of these curves in TLS 1.3.

This document provides the necessary protocol mechanisms for using
ECC Brainpool curves in TLS 1.3. This approach is not endorsed by 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 Feb 21 22:31:06 2020
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 BAE74120128 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 22:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 mhOeJ1db8nkW for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 22:31:02 -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 F056212013C for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Feb 2020 22:31:01 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 3FAA8F406DB; Fri, 21 Feb 2020 22:30:54 -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 45203F406DA; Fri, 21 Feb 2020 22:30:53 -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: <20200222063053.45203F406DA@rfc-editor.org>
Date: Fri, 21 Feb 2020 22:30:53 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8489_on_Session_Traversal_Utilities_for?= =?utf-8?q?_NAT_=28STUN=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, tram@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 8489

        Title:      Session Traversal Utilities for NAT (STUN) 
        Author:     M. Petit-Huguenin,
                    G. Salgueiro,
                    J. Rosenberg, 
                    D. Wing,
                    R. Mahy, 
                    P. Matthews
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    marc@petit-huguenin.org, 
                    gsalguei@cisco.com, 
                    jdrosen@jdrosen.net,
                    dwing-ietf@fuggles.com, 
                    rohan.ietf@gmail.com,
                    philip_matthews@magma.ca
        Pages:      67
        Obsoletes:  RFC 5389

        I-D Tag:    draft-ietf-tram-stunbis-21.txt

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

        DOI:        10.17487/RFC8489

Session Traversal Utilities for NAT (STUN) is a protocol that serves
as a tool for other protocols in dealing with NAT traversal.  It can
be used by an endpoint to determine the IP address and port allocated
to it by a NAT.  It can also be used to check connectivity between
two endpoints and as a keep-alive protocol to maintain NAT bindings.
STUN works with many existing NATs and does not require any special
behavior from them.

STUN is not a NAT traversal solution by itself.  Rather, it is a tool
to be used in the context of a NAT traversal solution.

This document obsoletes RFC 5389.


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.


[Note: This RFC is intentionally not published in the v3 format.]  

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 Feb 21 22:31:24 2020
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 7BC1D120289 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 22:31:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.201
X-Spam-Level:
X-Spam-Status: No, score=-5.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, 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 BwF3QM-J6eRc for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Fri, 21 Feb 2020 22:31:19 -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 D686A120828 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Fri, 21 Feb 2020 22:31:19 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 7A612F40721; Fri, 21 Feb 2020 22:30:59 -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 79FD2F4071A; Fri, 21 Feb 2020 22:30:58 -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: <20200222063058.79FD2F4071A@rfc-editor.org>
Date: Fri, 21 Feb 2020 22:30:58 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8656_on_Traversal_Using_Relays_around_N?= =?utf-8?q?AT_=28TURN=29=3A_Relay_Extensions_to_Session_Traversal_Utilitie?= =?utf-8?q?s_for_NAT_=28STUN=29?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, tram@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 8656

        Title:      Traversal Using Relays around NAT (TURN):
                    Relay Extensions to Session Traversal 
                    Utilities for NAT (STUN) 
        Author:     T. Reddy, Ed.,
                    A. Johnston, Ed.,
                    P. Matthews,
                    J. Rosenberg
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    kondtir@gmail.com, 
                    alan.b.johnston@gmail.com, 
                    philip_matthews@magma.ca,
                    jdrosen@jdrosen.net
        Pages:      79
        Obsoletes:  RFC 5766, RFC 6156

        I-D Tag:    draft-ietf-tram-turnbis-29.txt

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

        DOI:        10.17487/RFC8656

If a host is located behind a NAT, it can be impossible for that host
to communicate directly with other hosts (peers) in certain
situations. In these situations, it is necessary for the host to use
the services of an intermediate node that acts as a communication
relay. This specification defines a protocol, called "Traversal Using
Relays around NAT" (TURN), that allows the host to control the
operation of the relay and to exchange packets with its peers using
the relay. TURN differs from other relay control protocols in that it
allows a client to communicate with multiple peers using a single
relay address.

The TURN protocol was designed to be used as part of the Interactive
Connectivity Establishment (ICE) approach to NAT traversal, though it
can also be used without ICE.

This document obsoletes RFCs 5766 and 6156.

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  Sat Feb 22 15:05:50 2020
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 7DB7B3A0A30 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 22 Feb 2020 15:05:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 p25D0_67iyXM for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 22 Feb 2020 15:05:49 -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 6E6C03A0A33 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 22 Feb 2020 15:05:49 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id D0D2EF406D5; Sat, 22 Feb 2020 15:05:40 -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 86D30F406CC; Sat, 22 Feb 2020 15:05:39 -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: <20200222230539.86D30F406CC@rfc-editor.org>
Date: Sat, 22 Feb 2020 15:05:39 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8706_on_Restart_Signaling_for_IS-IS?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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: lsr@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 8706

        Title:      Restart Signaling for IS-IS 
        Author:     L. Ginsberg,
                    P. Wells
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    ginsberg@cisco.com, 
                    pauwells@cisco.com
        Pages:      22
        Obsoletes:  RFC 5306

        I-D Tag:    draft-ietf-lsr-isis-rfc5306bis-09.txt

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

        DOI:        10.17487/RFC8706

This document describes a mechanism for a restarting router to signal
to its neighbors that it is restarting, allowing them to reestablish
their adjacencies without cycling through the DOWN state while still
correctly initiating database synchronization.

This document additionally describes a mechanism for a router to
signal its neighbors that it is preparing to initiate a restart while
maintaining forwarding-plane state. This allows the neighbors to
maintain their adjacencies until the router has restarted but also
allows the neighbors to bring the adjacencies down in the event of
other topology changes.

This document additionally describes a mechanism for a restarting
router to determine when it has achieved Link State Protocol Data
Unit (LSP) database synchronization with its neighbors and a
mechanism to optimize LSP database synchronization while minimizing
transient routing disruption when a router starts.

This document obsoletes RFC 5306.

This document is a product of the Link State 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  Sat Feb 22 15:06:11 2020
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 7C5423A0AB0 for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 22 Feb 2020 15:06:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level:
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MAILING_LIST_MULTI=-1, 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 WQKb9DVa2mPe for <ietfarch-rfc-dist-archive@ietfa.amsl.com>; Sat, 22 Feb 2020 15:06:10 -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 668D03A0A52 for <rfc-dist-archive-yuw6Xa6hiena@ietf.org>; Sat, 22 Feb 2020 15:06:07 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 17E14F40704; Sat, 22 Feb 2020 15:05:48 -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 52487F406F7; Sat, 22 Feb 2020 15:05:47 -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: <20200222230547.52487F406F7@rfc-editor.org>
Date: Sat, 22 Feb 2020 15:05:47 -0800 (PST)
Subject: [rfc-dist] =?utf-8?q?RFC_8740_on_Using_TLS_1=2E3_with_HTTP/2?=
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.29
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, ietf-http-wg@w3.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 8740

        Title:      Using TLS 1.3 with HTTP/2 
        Author:     D. Benjamin
        Status:     Standards Track
        Stream:     IETF
        Date:       February 2020
        Mailbox:    davidben@google.com
        Pages:      5
        Updates:    RFC 7540

        I-D Tag:    draft-ietf-httpbis-http2-tls13-03.txt

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

        DOI:        10.17487/RFC8740

This document updates RFC 7540 by forbidding TLS 1.3 post-handshake
authentication, as an analog to the existing TLS 1.2 renegotiation
restriction.

This document is a product of the HTTP 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




















































































