Return-Path: 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 B3653126BFD for ; Mon, 8 May 2017 14:49:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.698 X-Spam-Level: X-Spam-Status: No, score=-2.698 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 4oufLWS6M78X for ; Mon, 8 May 2017 14:49:13 -0700 (PDT) Received: from mail-oi0-x236.google.com (mail-oi0-x236.google.com [IPv6:2607:f8b0:4003:c06::236]) (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 E5BBF124B0A for ; Mon, 8 May 2017 14:49:12 -0700 (PDT) Received: by mail-oi0-x236.google.com with SMTP id w10so66969619oif.0 for ; Mon, 08 May 2017 14:49:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PZn+ylRaoylQMb0nKnSZfvobcxU0q2aMdHZy27zfQpc=; b=myaJXyioqv2laI7+zvWX2WivEBZOI0NzdnXur8zdFimJeFBl6ZCWwBjdrKqRxMTtOz 6NmoE2aB8nMTHc/NCzdV8hOXtMH6HVHjMzlmO9JZnXuZj2TlsxbKBoQDvNV80uPPIS9s 519cmCZoq3FfnqCLD5nl9YnEumZRNec/n+CJ+cHQsPrKZfgTQR089Nd6G4c5PSmrj9f4 q9bp++EE1VBrEp+fBkQOdt836nT/0BLzM46XmPxZMAtS2ZmXw8CA5UoBLUYSD1aZYy/l 9aL4L3t5qjBmG6+OCBGw/x6O8udH53EoSnsM91tOXecFft11AmjO/Se1aZd0NUqj65SM F8NQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PZn+ylRaoylQMb0nKnSZfvobcxU0q2aMdHZy27zfQpc=; b=ShScNAgpNF5TcCU4UQ+1JU2PVa2n22/rcDKXhiTEenYgyObPJbObuP+1pVbf4RNpeB FhsL7/5foHqU9UEkyfXXouUfvoGlZjrC+ggF8wKudnBVklgJPh4bUvLK9733ds0drAVg 8I7n6GDTQQWn2yw13Hum4aVD6oWvgR+vDnoKcMgxswu0YuyH1idTxT88weUDkfvjEwMS uQ8lxV4G9lHaZJdURGDAr1Q3iH3+ZOaPkkWpT6JVswMAq0FmU30+S+hBm09jaO12XLpE V7Zp8TX7owMv0bsaasN2NpocCo/Fxqxo4q7T93WI4p2QKoTY8CcJix4k0xK9r8YX0bGs VC3Q== X-Gm-Message-State: AN3rC/7QNUO/hVaFpzv29oRklY1hr9DvwJmx0Kv+2fc0BUZdH62kz/bM ae3eGNJ9GABpGpMBDoiN/N165vpKS56oqNs= X-Received: by 10.157.43.210 with SMTP id u76mr24912180ota.223.1494280152308; Mon, 08 May 2017 14:49:12 -0700 (PDT) MIME-Version: 1.0 Received: by 10.157.52.246 with HTTP; Mon, 8 May 2017 14:49:11 -0700 (PDT) In-Reply-To: References: From: Greg Mirsky Date: Mon, 8 May 2017 14:49:11 -0700 Message-ID: To: "Acee Lindem (acee)" Cc: OSPF WG List Content-Type: multipart/alternative; boundary=001a113ade60ac6167054f0a356b Archived-At: Subject: Re: [OSPF] Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02) X-BeenThere: ospf@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: The Official IETF OSPG WG Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 May 2017 21:49:15 -0000 --001a113ade60ac6167054f0a356b Content-Type: text/plain; charset=UTF-8 Dear All, yes/support (readability needs some work) Couple nits: - Introduction. - Perhaps "Some networks use tunnels for a variety of reasons, such as:" may be re-worded as "There my be number of reasons why different types of tunneling technique has been used in networks, among these are:" - "The ingress needs to select a type of tunnel which is supported by the egress." I think that the idea is to find match between set of tunnels supported by the ingress and the egress. - Section 3 - s/Routers advertises/Routers advertise/ - It is stated that "The Encapsulation Capability TLV SHOULD NOT appear more than once within a given OSPF Router Information (RI) Opaque LSA." What happens when it does appear more than once? Discard LSA? TLV? Regards, Greg > > *From: *OSPF on behalf of "Acee Lindem (acee)" < > acee@cisco.com> > *Date: *Thursday, April 27, 2017 at 07:45 > *To: *"ospf@ietf.org" > *Subject: *[OSPF] Advertising Tunneling Capability in OSPF > (draft-ietf-ospf-encapsulation-cap-02) > > > > This begins the WG last call for the subject draft. Please send your > support and/or > > comments to this list prior to 12:00 AM GMT, May 12th, 2017. > > > > For your convenience, here is the URL for the subject document. > > > > https://www.ietf.org/id/draft-ietf-ospf-encapsulation-cap-02.txt > > > > Thanks, > > Acee > > > > _______________________________________________ OSPF mailing list > OSPF@ietf.org https://www.ietf.org/mailman/listinfo/ospf > > _______________________________________________ > OSPF mailing list > OSPF@ietf.org > https://www.ietf.org/mailman/listinfo/ospf > > --001a113ade60ac6167054f0a356b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Dear All,
yes/support (readability needs some work)

Couple nits:
  • Introduction.=C2=A0
    • Perhaps "Some networks use tunnels for a variety of reasons= , such as:" may be re-worded as "There my be number of reasons wh= y different types of tunneling technique has been used in networks, among t= hese are:"
    • "The ingress needs to select a type of tunnel = which is supported by the egress." I think that the idea is to find ma= tch between set of tunnels supported by the ingress and the egress.
    • Section 3
      • s/Routers advertises/Routers advertise/
        • It is stated that "The Encapsulation Capability TLV SHOULD NOT appear= more than once within a given OSPF Router Information (RI) Opaque LSA.&quo= t; What happens when it does appear more than once? Discard LSA? TLV?<= /ul>
      Regards,
      Greg

      <= div class=3D"gmail_quote">

      =C2=A0

      From: = OSPF <ospf-bounces@ietf.org> on b= ehalf of "Acee Lindem (acee)" <acee@cisco.com>
      Date: Thursday, April= 27, 2017 at 07:45
      To: "ospf@ietf.org" <ospf@ietf.org>
      Subje= ct: [OSPF] Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02)

      = =C2=A0

      This begins the WG last call f= or the subject draft. Please send your =C2=A0support and/or=C2=A0=

      comments to this list prior to 12:00 = AM GMT, May 12th, 2017.=C2=A0

      =C2=A0

      For your convenience, here is the URL for the subject docume= nt.=C2=A0

      =C2=A0

      <= a href=3D"https://www.ietf.org/id/draft-ietf-ospf-encapsulation-cap-02.txt"= target=3D"_blank">https://www.ietf.org/id/draft-ietf-ospf-encapsulati= on-cap-02.txt

      =C2=A0

      Thanks,

      Acee=C2=A0

      =C2=A0

      _______________________________________________ OSPF= mailing list OSPF@ietf.= org https://www.ietf.org/mailman/listinfo/ospf


      _______________________________________________
      OSPF mailing list
      OSPF@ietf.org
      https://www.ietf.org/mailman/listinfo/ospf


--001a113ade60ac6167054f0a356b--