IETF Logo Mail Archive

[RTG-DIR] RtgDir review: draft-rtg-dt-encap-02

Jamal Hadi Salim <hadi@mojatatu.com> Tue, 30 June 2015 12:21 UTC

Return-Path: <hadi@mojatatu.com>
X-Original-To: rtg-dir@ietfa.amsl.com
Delivered-To: rtg-dir@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A854B1A8AB6 for <rtg-dir@ietfa.amsl.com>; Tue, 30 Jun 2015 05:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.723
X-Spam-Level:
X-Spam-Status: No, score=0.723 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 8ilCXN9jfMoE for <rtg-dir@ietfa.amsl.com>; Tue, 30 Jun 2015 05:21:07 -0700 (PDT)
Received: from mail-ob0-f180.google.com (mail-ob0-f180.google.com [209.85.214.180]) (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 B5BBF1A8AB9 for <rtg-dir@ietf.org>; Tue, 30 Jun 2015 05:21:06 -0700 (PDT)
Received: by obdbs4 with SMTP id bs4so5092261obd.3 for <rtg-dir@ietf.org>; Tue, 30 Jun 2015 05:21:06 -0700 (PDT)
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:cc :content-type; bh=1yHbMle1Rw4ke7dtiA+yhAbctxNl0ZOtjWDlNRv7lYU=; b=ASoTN6SJQWIgx1uEFfG0SAFNjsZgw44fF73NCrx8B8ZCIS4W5v6x2IuE7l/u++i5J1 jyzyPglLK4pluGebYSuaJROg2X4oBz5YZa/emqgly0VVugQvDwvcXF41RQWlyAdSb8gV UtMSjrLpsYRqCyDIhoDEHkkEZ2A/gWUtJtqWa8ZROb+8HHvEEvEs9nT2mftgZKWjlvPi gsXWQaqIHMB85WYotx7ehQt7a10Z9YQHSnVOZuuQ4FLOVooo5SxtHVHHe+HNWX9snQ9g J5hAqwqcnRh+cZPQeV46qxY5991QTAdvI768oNyqgvKixXqAi+n/vhhh/6dIpfUfnluS 4erw==
X-Gm-Message-State: ALoCoQkeYrirbh1KzQ1e02UafCG3WLFxgIL34Tyzlrs/5Cak6viq6gxJFf9PULRE1RFXpvtum1Js
X-Received: by 10.182.153.197 with SMTP id vi5mr19101894obb.28.1435666865937; Tue, 30 Jun 2015 05:21:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.202.88.194 with HTTP; Tue, 30 Jun 2015 05:20:46 -0700 (PDT)
From: Jamal Hadi Salim <hadi@mojatatu.com>
Date: Tue, 30 Jun 2015 08:20:46 -0400
Message-ID: <CAAFAkD-vfrXA0ejLE7Gnk=q8wZbS4SzC7+=_TJY+qzTXv4R9OQ@mail.gmail.com>
To: "rtg-ads@tools.ietf.org" <rtg-ads@tools.ietf.org>
Content-Type: multipart/mixed; boundary="089e014953208fa4b00519bb3d5b"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dir/BssLWv2MeykaZT4BxjUw3K27CaU>
Cc: draft-rtg-dt-encap@tools.ietf.org, "rtg-dir@ietf.org" <rtg-dir@ietf.org>
Subject: [RTG-DIR] RtgDir review: draft-rtg-dt-encap-02
X-BeenThere: rtg-dir@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Directorate <rtg-dir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-dir/>
List-Post: <mailto:rtg-dir@ietf.org>
List-Help: <mailto:rtg-dir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dir>, <mailto:rtg-dir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2015 12:21:15 -0000

I have been selected as the Routing Directorate reviewer for this draft.
The Routing Directorate seeks to review all routing or routing-related
drafts as they pass through IETF last call and IESG review, and sometimes
on special request. The purpose of the review is to provide assistance to
the Routing ADs. For more information about the Routing Directorate, please
see http://trac.tools.ietf.org/area/rtg/trac/wiki/RtgDir

Although these comments are primarily for the use of the Routing ADs, it
would be helpful if you could consider them along with any other IETF
Last Call comments that you receive, and strive to resolve
them through discussion or by updating the draft.

Document: draft-rtg-dt-encap-02
Reviewer: Jamal Hadi Salim
Review Date: 6/30/15 (later than requested, sorry)
Intended Status: Informational
WG LC End Date: unknown

Summary:

The document has significant good work and recommendations for
encapsulation design. Many years of experience in issues found
with encapsulation deployments are discussed. There are times
where i lost track what the document was about because issues
were being discussed without making recommendations on what is needed
from an encapsulation perspective to deal with those issues; otoh,
a good read is section 18 which would mention an issue and in the
same breath suggests how a design should handle said issue.

The document needs at least one more pass.

I have some minor concerns about this document that I believe are
resolvable.
Annotated comments attached.

cheers,
jamal

v2.23.0 | Report a Bug | By Email