Subject: Re: [sidr] New Version Notification for draft-ietf-sidr-bgpsec-protocol-21.txt

From: "Sriram, Kotikalapudi (Fed)" <[email-masked]>
Date: Sat, 24 Dec 2016 00:33:49 +0000

This new version incorporates all (except two minor) comments received
during the IETF LC review process from Alvaro,  SECDIR/Gen-ART (Russ Housley),
and OPSDIR (Nevil Brownlee).

The two minor comments not addressed yet are from Russ,
and are pending feedback from WG members (particularly implementers).
These have to do with minor tweaks to the BGPsec update format structure.

Many thanks to Alvaro, Russ, and Nevil for the detailed reviews and comments/suggestions.

Sriram
________________________________________
From: [email-masked] <[email-masked]>
Sent: Friday, December 23, 2016 6:53 PM
To: Matthew Lepinski; Sriram, Kotikalapudi (Fed)
Subject: New Version Notification for draft-ietf-sidr-bgpsec-protocol-21.txt

A new version of I-D, draft-ietf-sidr-bgpsec-protocol-21.txt
has been successfully submitted by Kotikalapudi Sriram and posted to the
IETF repository.

Name:           draft-ietf-sidr-bgpsec-protocol
Revision:       21
Title:          BGPsec Protocol Specification
Document date:  2016-12-23
Group:          sidr
Pages:          41
URL:            https://www.ietf.org/internet-drafts/draft-ietf-sidr-bgpsec-protocol-21.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-protocol/
Htmlized:       https://tools.ietf.org/html/draft-ietf-sidr-bgpsec-protocol-21
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-bgpsec-protocol-21

Abstract:
   This document describes BGPsec, an extension to the Border Gateway
   Protocol (BGP) that provides security for the path of autonomous
   systems (ASes) through which a BGP update message passes.  BGPsec is
   implemented via an optional non-transitive BGP path attribute that
   carries digital signatures produced by each autonomous system that
   propagates the update message.  The digital signatures provide
   confidence that every AS on the path of ASes listed in the update
   message has explicitly authorized the advertisement of the route.

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat