Subject: [Sidrops] FW: New Version Notification for draft-ietf-sidr-bgpsec-protocol-23.txt

From: "Sriram, Kotikalapudi (Fed)" <[email-masked]>
Date: Thu, 27 Apr 2017 16:45:45 +0000

This new version is the “- publish an updated draft” step
in the process that Alvaro outlined (see his email attached below).
It also incorporates of a few editorial changes.

Sriram

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Thursday, April 27, 2017 12:02 PM
To: Matthew Lepinski <[email-masked]>; Sriram, Kotikalapudi (Fed) <[email-masked]>
Subject: New Version Notification for draft-ietf-sidr-bgpsec-protocol-23.txt

A new version of I-D, draft-ietf-sidr-bgpsec-protocol-23.txt

has been successfully submitted by Kotikalapudi Sriram and posted to the IETF repository.

Name:                 draft-ietf-sidr-bgpsec-protocol

Revision:            23

Title:                    BGPsec Protocol Specification

Document date:              2017-04-27

Group:                sidr

Pages:                 44

URL:            https://www.ietf.org/internet-drafts/draft-ietf-sidr-bgpsec-protocol-23.txt

Status:         https://datatracker.ietf.org/doc/draft-ietf-sidr-bgpsec-protocol/

Htmlized:       https://tools.ietf.org/html/draft-ietf-sidr-bgpsec-protocol-23

Htmlized:       https://datatracker.ietf.org/doc/html/draft-ietf-sidr-bgpsec-protocol-23

Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-sidr-bgpsec-protocol-23

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.

From: Alvaro Retana (aretana) [mailto:[email-masked]]
Sent: Wednesday, April 12, 2017 1:51 PM
To: [email-masked]
Cc: [email-masked]; [email-masked]; [email-masked]; [email-masked]
Subject: Re: BGPsec without Extended Messages (draft-ietf-sidr-bgpsec-protocol)

Hi!

Thanks to everyone who made comments in support for the modified text.

I am now proceeding with the rest of the process (below).  Will cc the WG as needed.

Thanks!!

Alvaro.

On 4/4/17, 12:15 PM, "Alvaro Retana (aretana)" <[email-masked]<mailto:[email-masked]>> wrote:

Given that this document has already been approved by the IESG, the process going forward is:

- consult the WG (this thread)
- inform the IESG of the intent
- inform the IETF ([email-masked])<mailto:[email-masked])> of the changes
- publish an updated draft
- continue the publication process

Each step may, obviously, require additional discussion and could result in changes to the current plan.