[OSPF] draft-ietf-ospf-transition-to-ospfv3-11

Alia Atlas <akatlas@gmail.com> Fri, 01 July 2016 16:10 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58EDF12D759 for <ospf@ietfa.amsl.com>; Fri, 1 Jul 2016 09:10:54 -0700 (PDT)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 2v6i4lcfxGou for <ospf@ietfa.amsl.com>; Fri, 1 Jul 2016 09:10:52 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 BDB7212D756 for <ospf@ietf.org>; Fri, 1 Jul 2016 09:10:52 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id t127so209686820qkf.1 for <ospf@ietf.org>; Fri, 01 Jul 2016 09:10:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=eKOpMTc1wA/ODPOiKxac/a+/uL+UfqSfMwcoGTNV+4A=; b=aQfIyOgSZ2t1weRTnk0rJB3i370icw4eY8ZK+O8q17MyMnDU+2K8sSAl9YJYztt/pH 0RLf4ehrpXJnf9cUZY7ibp8Skoj1j0rFQelZSUVVXitPgm2s5usTUT8Bz6drRRi6EXYd Yc+WCHypJoglkrt0HSjSdKL7hRP8qFug9WYP13iOm3wkGDH/EKtMh4yAAl+pgX4gKv2n frnS2rWHOohtJ26cl7TeB/zP7Z8wD1weFAZb0vpTRlHZWw7rKMceRbQIXq6WXsGTiane YwxGrsxWESD7nVoPO5wJAvf2cOGJJPdQi3KyNB42GSmGyzVlp6BCxpvIg5S567NDMrHi qfyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=eKOpMTc1wA/ODPOiKxac/a+/uL+UfqSfMwcoGTNV+4A=; b=dqby8qy18YmFF20d0epnBKkPQNPhAwNY8DeNnenKgBI2w00l3Xgyzs0rBQu2zHAyRn gG5uVVc2h04r0N+akYZo/mh9ynZvCNCeFFW/620lFONI+UBJ1c/GLrVsBsj7cZ+D1WkR AnBj8JI1eLAsnUurEiX1qHP9CM4F+Be6Prn3vZtLa7Fi2Lhf3uDOW/sn1vvET1tqbOn0 sJyrweGesiUn0gbBXFjjuG+q8G/YRedfmszW6OpVemMKClhwAbce7q9n/ULl3pf6mxAJ UWCj61py7J9pLMK4Q0FVZ1PMumBYXwOOd2N7yYvPjf29rU24yi/EaLeTZ9oFVWm/e00v bJVA==
X-Gm-Message-State: ALyK8tIyCFGkeDYfEhn2tPBzcp2v6zYdvjj6pdCCO2oE4+emLuMNvYoSQfEUkKromcg8lugdv6qR2XnD/9riBg==
X-Received: by 10.55.87.194 with SMTP id l185mr28917095qkb.204.1467389451719; Fri, 01 Jul 2016 09:10:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.57.81 with HTTP; Fri, 1 Jul 2016 09:10:51 -0700 (PDT)
From: Alia Atlas <akatlas@gmail.com>
Date: Fri, 1 Jul 2016 12:10:51 -0400
Message-ID: <CAG4d1rccQ+Mk2L=SbL-jH3Y7HZD+b9g9i0rcCBogv7UxYZRsvA@mail.gmail.com>
To: OSPF List <ospf@ietf.org>
Content-Type: multipart/alternative; boundary=001a114e7322045ac30536953b5e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/1vFxxgoGUQMUHIZOAohg9q109CA>
Subject: [OSPF] draft-ietf-ospf-transition-to-ospfv3-11
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jul 2016 16:10:54 -0000

There were a couple clarifications - most notably clarifying the
pseudo-header being used to calculate the checksum.

I have approved the draft to proceed to the RFC Editor, but would recommend
those interested
read this version.

Obviously, if necessary, clarifications are still possible during AUTH48.

Regards,
Alia