Re: [i2rs] WG adoption - draft-hares-i2rs-auth-trans-04 (8/17 to 8/31)

Daniel Migault <daniel.migault@ericsson.com> Fri, 21 August 2015 13:50 UTC

Return-Path: <mglt.ietf@gmail.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 586831A9050 for <i2rs@ietfa.amsl.com>; Fri, 21 Aug 2015 06:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 PFdfFxgtwbDm for <i2rs@ietfa.amsl.com>; Fri, 21 Aug 2015 06:50:51 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 096401A905B for <i2rs@ietf.org>; Fri, 21 Aug 2015 06:50:51 -0700 (PDT)
Received: by iodv127 with SMTP id v127so81889380iod.3 for <i2rs@ietf.org>; Fri, 21 Aug 2015 06:50:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=1iK3l16MLAUbtF/PzWDvQualG1igZFHfeCo1VQwhJc8=; b=jXXG7M8x59eme3H7T4AJVO8FMpXmTz1WCi+FOW13eLeGE5wsTkEtdGMQUr8rUQONjY b2V/bh3G2OVz1QqoglLrytQeQ/AYTwnDRV8TX9Q1Zyyt1my83QHedZl46kMHRk6WzHox zuMZ97VGj+tnliBTeyKaYPRyWBislXRFID3mTJ5e4V5nUGyjF0d4cxaXVHSO/p3Z7qCu IJfv7/rR2DSGck+lYYsd5xHopc1MgQDnwpuVZSDi8qxc3msqQfA65y07xE5JxUKWax76 q8x9WXzRCGltME65YfyHcH8A76D9b4Q7Y7U6Feut/ENkxlxhaKDrSwoxXpV/sxyHEX00 ubCw==
MIME-Version: 1.0
X-Received: by 10.107.37.12 with SMTP id l12mr5231317iol.92.1440165050468; Fri, 21 Aug 2015 06:50:50 -0700 (PDT)
Sender: mglt.ietf@gmail.com
Received: by 10.79.21.196 with HTTP; Fri, 21 Aug 2015 06:50:50 -0700 (PDT)
In-Reply-To: <019b01d0d914$24c02590$6e4070b0$@ndzh.com>
References: <019b01d0d914$24c02590$6e4070b0$@ndzh.com>
Date: Fri, 21 Aug 2015 09:50:50 -0400
X-Google-Sender-Auth: VUbSVjUvTzF15xVwnc1uvByRUHI
Message-ID: <CADZyTkmVaYUQb9LL=zQh80tX54mGmDOLnL4ZPO7MVVh=mWqgVw@mail.gmail.com>
From: Daniel Migault <daniel.migault@ericsson.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary="001a1141b24e404f7d051dd28e5a"
Archived-At: <http://mailarchive.ietf.org/arch/msg/i2rs/dwXDsU9ZrAcZKBPALtwtZauL-Vw>
Cc: Jeffrey Haas <jhaas@pfrc.org>, i2rs@ietf.org
Subject: Re: [i2rs] WG adoption - draft-hares-i2rs-auth-trans-04 (8/17 to 8/31)
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 21 Aug 2015 13:50:53 -0000

As a co-author of the document, I believe the document is ready for
adoption. Feel free to comment so we can improve the document for its next
iteration.

I also support the two documents as it appears to be much cleaner to have
two separate documents.

BR,
Daniel

On Mon, Aug 17, 2015 at 1:42 PM, Susan Hares <shares@ndzh.com> wrote:

> This is a 2 week WG adoption call for the
> draft-hares-i2rs-auth-trans-04.txt which provides the security requirements
> for the I2RS protocol.
>
>
>
> To be adopted, this draft does not need to be perfect, but a good
> direction for the I2RS protocol security.
>
>
>
> Please note that Juergen’s review of this draft has the following feedback:
>
> •       Requirements 1, 2, 5, 6, 7, 9, 11, 13, 14, 15, 16, 18, 19, 20 –
> were ok,
>
> •       Editorial requirements 3 and 4 need clarifications on words, and
> requirement 10 is ambiguous, and
>
> •       Requirements 8, 12, and the multiple message sequence (was
> req-17) are not security protocols,
>
> •       Technical question: Why should we support an insecure protocol.
>
>
>
> A security directorate reviewer will review this draft starting on 8/20.
> I will post these reviews and the document changes.  Please suggest changes
> to requirement 3, 4, and 10; and if I2RS should support an insecure
> protocol.
>
>
>
> Once we get the security reviewers feedback on 8, 12, and the multiple
> messages – I will post the feedback and we’ll discuss real time.
>
>
>
> *Sue Hares *
>
>
>
> _______________________________________________
> i2rs mailing list
> i2rs@ietf.org
> https://www.ietf.org/mailman/listinfo/i2rs
>
>