[Idr] AD review and progression of draft-ietf-idr-as-migration-03
Alia Atlas <akatlas@gmail.com> Fri, 30 January 2015 19:46 UTC
Return-Path: <akatlas@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F36221A1BB8 for <idr@ietfa.amsl.com>; Fri, 30 Jan 2015 11:46:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.999
X-Spam-Level:
X-Spam-Status: No, score=-101.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 dDsVQZnPheFE for <idr@ietfa.amsl.com>; Fri, 30 Jan 2015 11:46:31 -0800 (PST)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0BC71A1BB4 for <idr@ietf.org>; Fri, 30 Jan 2015 11:46:31 -0800 (PST)
Received: by mail-yh0-f50.google.com with SMTP id t59so11761137yho.9 for <idr@ietf.org>; Fri, 30 Jan 2015 11:46:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=aUJy5UA2hTQ/YbOf9Z9UCGMiefLnmOBGITKHG0HNAVY=; b=n1KH/msrs2wSVfrWcrZJ9dIENxnpqxII8Ntp1Cik4WnyKy0PAIzkNpQOjmHxw/ZATx 33UWqCqK9y+qzY+1Y7ZWL54UlmAQxWvqeQdnKQ3+DqaqIfPRALxeZrJ6Nc0FwqHE+V3c cahH8mxJ4ow4MHeaQ5W/OYjnUY9tT8WaycXJI2dkvJ58rEjvp2O+MgEFhrnHAJ1TuReO iTl5oI1VCz1ayVCcLWuU4WRF+HfValr7vCxOPH4DGu2bQmSprCRq9dObLDAtce7qy0IO Ufbuxedwm6gWSlpAZ+HjlM44ETjXGdryXifcIKKujzSg601Gk5knJ3ozuiGraXGO3yZn USJg==
MIME-Version: 1.0
X-Received: by 10.236.27.75 with SMTP id d51mr3911860yha.60.1422647190945; Fri, 30 Jan 2015 11:46:30 -0800 (PST)
Received: by 10.170.133.80 with HTTP; Fri, 30 Jan 2015 11:46:30 -0800 (PST)
Date: Fri, 30 Jan 2015 14:46:30 -0500
Message-ID: <CAG4d1rcCHcogajQjWtLAd7gu-ZtNUGQaPDyRd14YEkh1K4C2KQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
To: draft-ietf-idr-as-migration@tools.ietf.org
Content-Type: multipart/alternative; boundary="089e0160be8e750540050de3dc77"
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/Dnsuq5c0OJRwZ7Gy_dztxnXrD4g>
Cc: "idr@ietf. org" <idr@ietf.org>
Subject: [Idr] AD review and progression of draft-ietf-idr-as-migration-03
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jan 2015 19:46:33 -0000
I have done my standard AD review of this useful and clear draft. First, I would recommend strengthening the security considerations with a reference to the existing BGP security mechanisms. Second, based on a reading of RFC 3967 and how this draft uses the AS numbers for an example, I believe that the reference should be informative. Please handle these issues during IETF Last Call. I'm putting this into IETF Last Call and on the IESG telechat for Feb 19. Thanks for the good work! Alia
- Re: [Idr] AD review and progression of draft-ietf… George, Wes
- [Idr] AD review and progression of draft-ietf-idr… Alia Atlas
- Re: [Idr] AD review and progression of draft-ietf… George, Wes
- Re: [Idr] AD review and progression of draft-ietf… Alia Atlas
- Re: [Idr] AD review and progression of draft-ietf… Alvaro Retana (aretana)