[i2rs] 2 week WG LC for draft-ietf-i2rs-traceabilty
"Susan Hares" <shares@ndzh.com> Tue, 26 May 2015 21:54 UTC
Return-Path: <shares@ndzh.com>
X-Original-To: i2rs@ietfa.amsl.com
Delivered-To: i2rs@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09AA11B3222; Tue, 26 May 2015 14:54:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.155
X-Spam-Level:
X-Spam-Status: No, score=-97.155 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100] autolearn=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 S790X8F1Q_OI; Tue, 26 May 2015 14:54:45 -0700 (PDT)
Received: from hickoryhill-consulting.com (hhc-web3.hickoryhill-consulting.com [64.9.205.143]) by ietfa.amsl.com (Postfix) with ESMTP id BBA2E1B3224; Tue, 26 May 2015 14:54:33 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=174.124.178.112;
From: Susan Hares <shares@ndzh.com>
To: i2rs@ietf.org
Date: Tue, 26 May 2015 17:54:31 -0400
Message-ID: <012701d097fe$8c8554e0$a58ffea0$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0128_01D097DD.0576C220"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdCX/brn0dvPMo3GSuqLIt07oHEavg==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/u8yTw8xNjsD1C8CQcFS1iKd8fc0>
Cc: cpignata@cisco.com, netmod@ietf.org, jclarke@cisco.com, "'Gonzalo Salgueiro (gsalguei)'" <gsalguei@cisco.com>, 'Alia Atlas' <akatlas@juniper.net>, netconf@ietf.org, 'Jeffrey Haas' <jhaas@pfrc.org>
Subject: [i2rs] 2 week WG LC for draft-ietf-i2rs-traceabilty
X-BeenThere: i2rs@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Interface to The Internet Routing System \(IRS\)" <i2rs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i2rs>, <mailto:i2rs-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i2rs/>
List-Post: <mailto:i2rs@ietf.org>
List-Help: <mailto:i2rs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i2rs>, <mailto:i2rs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 May 2015 21:54:47 -0000
This begins a 2 week WG LC for <http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/> draft-ietf-i2rs-traceability-02 from (5/26 to 6/9) (http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/) I2RS Status: WG LC (5/26 to 6/9) Carlos, joe, and Gonzalo - please indicate whether you know of any IPR on this draft. This document is a companion to three other documents for I2RS requirements which have WG calls: 1) This begins a 2 week adoption call for draft-haas-i2rs-ephemeral-state-req: https://datatracker.ietf.org/doc/draft-haas-i2rs-ephemeral-state-reqs/ This document covers requests to the netmod and netconf Working Groups for functionality to support the ephemeral state requirements to implement the I2RS architecture. Status: WG adoption call (5/26 to 6/9) 2) <http://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements /> draft-haas-i2rs-netmod-netconf-requirements-01 http://datatracker.ietf.org/doc/draft-haas-i2rs-netmod-netconf-requirements/ [This draft is an early set of requirements from which the ephemeral state and "identity, secondary-identity and priority" were pulled into draft-haas-i2rs-ephemeral-state-reqs. The notification-subscription were pulled into the draft-ietf-i2rs-pub-sub-requirments. The traceability had been separated before draft-haas-i2rs-nemod-netconf-requirements was published. This draft remains the only source for mutual authentication requirements (section 2.2), transaction requirements, and the history of the discussion. This draft is being requested to be adopted as a general roadmap for the I2RS WG. In the future, the I2RS WG will accept more detailed specification on the mutual authentication or the transaction protocol. I2RS Status: WG Adoption (5/26 to 6/9) 3) draf-ietf-i2rs-pub-sub-requirements-02. http://datatracker.ietf.org/doc/draft-ietf-i2rs-pub-sub-requirements/ I2RS Status: WG LC (5/26 to 6/9) This thread is to discuss WG consensus on <http://datatracker.ietf.org/doc/draft-ietf-i2rs-traceability/> draft-ietf-i2rs-traceability-02 . Please discuss the merits of the traceability framework described in this draft as being part of the requirements forwarded to netmod/netconf. Also discuss if this framework provides the necessary things for I2RS deployment. This draft will also be forwarded as part of the requirements to the IESG. Sue Hares
- [i2rs] 2 week WG LC for draft-ietf-i2rs-traceabil… Susan Hares
- Re: [i2rs] 2 week WG LC for draft-ietf-i2rs-trace… Gonzalo Salgueiro (gsalguei)
- Re: [i2rs] 2 week WG LC for draft-ietf-i2rs-trace… Joe Clarke
- Re: [i2rs] 2 week WG LC for draft-ietf-i2rs-trace… Carlos Pignataro (cpignata)