Return-Path: X-Original-To: idr@ietfa.amsl.com Delivered-To: idr@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C850E120150; Wed, 12 Jun 2019 04:06:16 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 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_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 gd8V172G2TPR; Wed, 12 Jun 2019 04:06:14 -0700 (PDT) Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) (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 A346E120124; Wed, 12 Jun 2019 04:06:14 -0700 (PDT) Received: by mail-ed1-x52f.google.com with SMTP id w33so25071902edb.10; Wed, 12 Jun 2019 04:06:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=NB33Yve3Cu6xVCC9xSlsvV9nEkcaGd2Iv6nAJYOXycU=; b=odo4WZhhm/cNWHRba2cB08LSNO5TC7H7mvTJR4laUlxLQ61Qyec4i1DBzXazffvHn/ 3ql1C80gftL915k1zVJ3R7Yt1biQ/XyRJZpkaeFEoqEt7bzyIZ+chCu9WrXpaZmP0zsy 8VxjQIWRfPL2GrRdGx6ocuKliB1BtO1zdOBtOErh8DVaT0M3JWRM8XGaD70ReMHi27G3 v8dBlWKD8m1k2HxUky+c0sSO05Q2DWNmbniaNcjzjBxEEMCjObiG/ikrSWdNKJFKJRzM K0B5fSC5seKLj94rVjjTEdFX+jQ2Yxws9PXi0C5rX5mfiZsW4w6rzPJ7D+NleR667+QO OwgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=NB33Yve3Cu6xVCC9xSlsvV9nEkcaGd2Iv6nAJYOXycU=; b=e8kq9zpVVFn+KEM5lUJtyQYp4PwlP7ARozL0tJVaNeQ4ehMRKNuR/yjqwfDJ/zjocI Y1PIvK6Yi/V+5XGkCcsP5JbxtB0+sowkwO4C6TNKPiyqgCzYKIOj4SXApv7rwLHuLKvs ICPieWFOJhxm8TH4YqTdBFunzye7nQDg59oxD4WdaKdUzXbuA+O6iZLVI95fRZUNuXQ+ y/Op1Gj3bHSpUXjT4PVHJud4GDzcqQdwYSByxH5a9pXH9l+6vA2ARj3UiNuQcu4LKcMW FwQwtE7BQRO7busG1jCX/OAvUs4R0jw5ctGAEV7ozbshqE/nfeM+o8t/nqjMUeigEuQT pnzw== X-Gm-Message-State: APjAAAV55qgkvYY1tiIf9kWnW3ZPOCraVniou9aOBLkFE5ZiHgjOvzIj 64Ze0peUT9JBJ6VVLj0ju6e8+O2qprMv4+rKs6htJA== X-Google-Smtp-Source: APXvYqxomt2EIHoNW6O+fBOCW0MJmBNO2OL0LaPeT5FtpELpj9tUmuS5vgqrglEdvp0ggtQV6d16anga94UPCGwXBVc= X-Received: by 2002:a50:ad7d:: with SMTP id z58mr64430794edc.277.1560337572884; Wed, 12 Jun 2019 04:06:12 -0700 (PDT) Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 12 Jun 2019 07:06:11 -0400 From: Alvaro Retana In-Reply-To: <156030307145.5955.16632008914934707005.idtracker@ietfa.amsl.com> References: <156030307145.5955.16632008914934707005.idtracker@ietfa.amsl.com> MIME-Version: 1.0 Date: Wed, 12 Jun 2019 07:06:11 -0400 Message-ID: To: The IESG , Roman Danyliw Cc: Susan Hares , idr-chairs@ietf.org, idr@ietf.org, draft-ietf-idr-bgp-ls-segment-routing-ext@ietf.org Content-Type: multipart/alternative; boundary="000000000000c2f33a058b1e6673" Archived-At: Subject: Re: [Idr] Roman Danyliw's No Objection on draft-ietf-idr-bgp-ls-segment-routing-ext-15: (with COMMENT) X-BeenThere: idr@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Inter-Domain Routing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2019 11:06:17 -0000 --000000000000c2f33a058b1e6673 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On June 11, 2019 at 9:31:12 PM, Roman Danyliw via Datatracker ( noreply@ietf.org) wrote: Roman: Hi! Just answering this first question: (1) Section 2.0. Does the sentence, =E2=80=9CThis document adds additional = BGP-LS Attribute TLVs in order to encode SR information=E2=80=9D imply that this d= ocument should explicitly update RFC7752? No. rfc7752 is the base BGP-LS specification=E2=80=A6some TLVs are defined ther= e. This document extends BGP-LS with more TLVs to support Segment Routing=E2=80=A6b= ut this is an independent extension: not all rfc7752-compliant implementations have to support SR. Thanks! Alvaro. --000000000000c2f33a058b1e6673 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =
On June 11, 2019 at 9:31:12 PM, Roman Danyliw via Datat= racker (noreply@ietf.org) wrote:

Roman:

Hi!

Just answering this first question:
=

= (1) Section 2.0. Does the sentence, =E2=80=9CThis document ad= ds additional BGP-LS=C2=A0
Attribute TLVs in order to encode SR info= rmation=E2=80=9D imply that this document=C2=A0
should explicitly up= date RFC7752?=C2=A0

No. =C2=A0

rfc7752 is the base BGP-LS = specification=E2=80=A6some TLVs are defined there.=C2=A0 This document exte= nds BGP-LS with more TLVs to support Segment Routing=E2=80=A6but this is an= independent extension: not all rfc7752-compliant implementations have to s= upport SR.

Thanks!

Alvaro.
--000000000000c2f33a058b1e6673--