[Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy

Chaitanya Varma <chaitanya.varma@ipinfusion.com> Tue, 30 April 2019 08:04 UTC

Return-Path: <chaitanya.varma@ipinfusion.com>
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 5A7B31200F5 for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 01:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.333
X-Spam-Level:
X-Spam-Status: No, score=-1.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipinfusion.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 KAdyxMz9_Qr9 for <idr@ietfa.amsl.com>; Tue, 30 Apr 2019 01:04:34 -0700 (PDT)
Received: from mta.hdems.com (mta19.mta.hdems.com [52.198.247.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5207C120099 for <idr@ietf.org>; Tue, 30 Apr 2019 01:04:34 -0700 (PDT)
Received: from mo.hdems.com (unknown [10.5.84.254]) by mta-c04-s0801.mta.hdems.com ('HDEMS') with ESMTPSA id 44tYw11XJMz1l for <idr@ietf.org>; Tue, 30 Apr 2019 08:04:33 +0000 (UTC)
X-HDEMS-MO-TENANT: access-company.com
Received: from mail-it1-f197.google.com (mail-it1-f197.google.com. [209.85.166.197]) by gwsmtp.prod.mo.hdems.com with ESMTPS id gwsmtpd-trans-bb64a905-2418-4812-b7d5-7d0b130ccfab for <idr@ietf.org>; Tue, 30 Apr 2019 08:04:30 +0000
Received: by mail-it1-f197.google.com with SMTP id h69so1699198itb.5 for <idr@ietf.org>; Tue, 30 Apr 2019 01:04:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipinfusion.com; s=google; h=from:mime-version:thread-index:date:message-id:subject:to:cc; bh=emCq+hMAIDR44GXFkaWwE1AqBQxdB1pDqxwFY4aag4k=; b=BLjYSjtiU7q3oDqUJkLuHmbWPyUFyCrPsgo9vdwbb0UaCD8Gdw6gpCTkUcQJR29Vkr rFRelU9dpbWaY9OIetS8tnSpHGM4uJlmcB4rpZXV3WoS/8tBMo8rTJKzJAx44oX4QBsd 6nXwKglknj3eMEcLqZ2PW0oV2Gi7T1VEgX9PokGAXxDagoscMK+Oqijzlf71AZU8UuXE u71xA+Up+HZwtiJlvqNZj4TgztsxfSPFIlD2StsjLEWZcOCb3jF0fwGfUuTSwzIrKlj9 JP44Tq9d++hGKrleUou0QG0csLwb5ARl8XJvyfDTcMe7RbXsaWhAEOAC7BpIS15DiZNv RpPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:thread-index:date:message-id :subject:to:cc; bh=emCq+hMAIDR44GXFkaWwE1AqBQxdB1pDqxwFY4aag4k=; b=b5qsQ95CyMfV7achxVIcfWzPZe0OoOMaALnYXfIhGKUnzpUB6+1LPhJBYsHIs4/sOw Et7n+UcTmoLPvQpENqj3d98bO8vAhoxEfwaLuD1XtcNpdIdTR8i/M58Dh7vDRmZlz8K/ yEX/X+aQpPLtEW/mKrk7xOu+P7gSsXpPMfgaDJrtCNvSZOPj53DjM5OOVPyGwn6xXTig QrDEV4/pWTomMJdAIR5mdeFZvXBcL2qVpW9HMOON+yPaL6y1BLoz2Z0XhYGAaVKEebk/ IY8o0HoUhPNOsN/I0rc50NqueCjJeW9ZHWqJPXgxAuGJQtSFVRXev+jBO/VwwzX4rOi3 6IUA==
X-Gm-Message-State: APjAAAW5H9fCqRZm4KAnvQeNK824tO73wBzwsDHswrAUvP7+SzvFbq9w swG15ktHJJvWeLpkbeO1Jj5bsrTIGk3ugv4GsHQU6LVbiYxwq6mtwxriG3N6uYrlaX+ACHJ1FDm NQnwXR6cdlY9HT7P7CAf9FtYc4PfsaxSFh/Rov/sXw/Y9/QeRq+RfWMZKrMesAKSb0vxUypYLIr ZJOyfNXL4HcrdL9ChWC4u1Bw3yISNkr1tkgQ==
X-Received: by 2002:a6b:8b95:: with SMTP id n143mr6498571iod.179.1556611468963; Tue, 30 Apr 2019 01:04:28 -0700 (PDT)
X-Google-Smtp-Source: APXvYqwe+fEC0n97lMOq1KaiA7WR9Bs4ppxYOWvaNu8tkLMKP6OsVskQXDJFgrhUGLOQ3te2S+UN2OcZK+2Vt/fVy1s=
X-Received: by 2002:a6b:8b95:: with SMTP id n143mr6498550iod.179.1556611468603; Tue, 30 Apr 2019 01:04:28 -0700 (PDT)
From: Chaitanya Varma <chaitanya.varma@ipinfusion.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdT/KtjPP6BADXj+R+K+v5ydxRQvuQ==
Date: Tue, 30 Apr 2019 13:34:26 +0530
Message-ID: <993db9e45983acc9769af61bf786a6d6@mail.gmail.com>
To: idr@ietf.org
Cc: Gurusiddesh Nidasesi <gurusiddesh.nidasesi@ipinfusion.com>
Content-Type: multipart/alternative; boundary="000000000000a3cad50587bad963"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/Tiouxc1_0GbuXkSGWfyWpwebJSg>
X-Mailman-Approved-At: Tue, 30 Apr 2019 08:18:38 -0700
Subject: [Idr] Mail regarding draft-ietf-idr-segment-routing-te-policy
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 30 Apr 2019 08:07:17 -0000

Hi,



I have couple of queries from the below draft.



https://tools.ietf.org/html/draft-ietf-idr-segment-routing-te-policy-05



*  “ Typically, a controller defines the set of policies and advertise*

*   them to policy head-end routers (typically ingress routers).” *



How do we communicate SR policies from controller? Is it through BGP-SR
session or PCEP session.

a. If it is through PCEP session what happens if the PCC is non-headend?

b. If it is through BGP-SR what is the role for PCEP between PCE and PCC?

*  “ Moreover, one or more route-target SHOULD be attached to the*



*   advertisement”*How Route-target should be attached to a SR-NLRI update?

Is it done through local configuration or picked up based on some dynamic
parameter?



Appreciate if you can help here.





Regards,

Chaitanya

-- 
.