Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer Intra vs Inter-domain
Dhruv Dhody <dd@dhruvdhody.com> Tue, 19 September 2023 03:49 UTC
Return-Path: <dd@dhruvdhody.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB080C151076 for <pce@ietfa.amsl.com>; Mon, 18 Sep 2023 20:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dhruvdhody-com.20230601.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s54I1ERZYQzL for <pce@ietfa.amsl.com>; Mon, 18 Sep 2023 20:49:06 -0700 (PDT)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ED6DC15108B for <pce@ietf.org>; Mon, 18 Sep 2023 20:49:06 -0700 (PDT)
Received: by mail-vs1-xe2c.google.com with SMTP id ada2fe7eead31-452749f6c47so703153137.1 for <pce@ietf.org>; Mon, 18 Sep 2023 20:49:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20230601.gappssmtp.com; s=20230601; t=1695095345; x=1695700145; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=m9HWCYQLTrb/+SyCXhDSG+3tLAv2/Zxys9VE8xHsbH0=; b=jl0R6uePAKX4iuLXIptfZIPt7K5NC3ZGrSh259HY55s5N42xvxLKiLoM9HtQ1E/g1Q BpkGMiJ6ntvK7XioySlz59gd3w9nikT91VHuGHLCaKPzkEBskEhlHfK/AWKbbOD8kzaA 0dWm4ViZkUnD76NwmZpbgt9v4sH+niyU8OuVqktm14I6SmklTtF5pi9C+oA7wjo8gdYe E/6ubmTSaGf4+2lCF9Hl0lvRE3EbFRc8x5CZ1BTV5m9rbPPdtVEOZWhszWmq1rlI6cEH N3TpPfpol0YrUX+pZT4bEibMU6hnmeI+pq7EcHPj+OAZriAAewzcRkeJG50b28BmgpjU vh5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695095345; x=1695700145; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=m9HWCYQLTrb/+SyCXhDSG+3tLAv2/Zxys9VE8xHsbH0=; b=srlh7ySf9L7q3Dn0aPMl2LxUVND+0kwusoWHcD9s9I1x9oyWljl/psppZ/FIowpOW4 kLNteWG4uGIJ1qqgI+zXzMZuEePk2KxJewPIB800daqLIZ9OEj2AqpsWv0ycJX7RjSHT sG6KrUAr2gwrHPHz7wcKbpQgM6hEd4vY9Cpm56Fu6zPeHuJD33YARS48HzvTcg/KCPs/ lSdNYbgC5QAFoNeZB2P6wLbrgBGXsC4R0KOkWHF7V2RkuHVdlFfBIrRPb4YXUm9/Trsy 9XGhyXYrXN7QFUtFAw2ISugkM5gASnoD6Qxj0NCDKz6s7zS9rjP8xAlRl/xAx0jmDrKS DoEA==
X-Gm-Message-State: AOJu0Yy7fXqyww2Q3GGPH25sw2erqubYQDs2xeJKww02hy2CpcuQjYal QB9hK8uiHlWJBmgwN9B4EVw+xUY+Mdl0cj+Vr3aaIw==
X-Google-Smtp-Source: AGHT+IEtB3FAMkqPQXnvW20bUEf9dSINciUg1wWTfqScZR8XgggoF+rqR4mU3qi10bHr29M9lymXHuQ7kc6lfJs1lN0=
X-Received: by 2002:a05:6102:468c:b0:452:721b:1cae with SMTP id dw12-20020a056102468c00b00452721b1caemr3547337vsb.0.1695095345552; Mon, 18 Sep 2023 20:49:05 -0700 (PDT)
MIME-Version: 1.0
References: <AM9PR06MB72041F2F6B7C55B09EB59D67A9F6A@AM9PR06MB7204.eurprd06.prod.outlook.com> <202309191134225633192@zte.com.cn>
In-Reply-To: <202309191134225633192@zte.com.cn>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Tue, 19 Sep 2023 09:18:28 +0530
Message-ID: <CAP7zK5Z9FFzcyAR_8zwA=SBDGcf-nkPoPN5+cCJcoSs=8yb-Rw@mail.gmail.com>
To: peng.shaofu@zte.com.cn
Cc: marcel.reuter.external@telefonica.com, pce@ietf.org
Content-Type: multipart/alternative; boundary="000000000000eeb31e0605ae23af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/lFPQj-QcKcur5OQ3gngF_Cc6mdM>
Subject: Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer Intra vs Inter-domain
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Sep 2023 03:49:11 -0000
Hi Marcel, PSF, Speaking as a WG participant... Note that we do have a metric type "T=20: Domain Count metric (number of domains crossed)."; we can simply use this metric type, asking the PCE to optimize based on this which should lead to preferring intra-domain paths. See https://www.rfc-editor.org/rfc/rfc8685.html#section-3.5 Thanks! Dhruv On Tue, Sep 19, 2023 at 9:04 AM <peng.shaofu@zte.com.cn> wrote: > > Hi Marcel, > > > May it be a local policy of PCE ? > > For a given <ingress PE, egress PE> that belongs to the same domain, it > may be > > the default policy for PCE to calculate a candidate path intra domain. > > Otherwise, it may bring unnecessary complexity. For example, for a real > inter-domain > > path requirement of <ingress PE, egress PE> that belongs to the different > domain, > > the intention is to split the path calculation requirements into multiple > domains, e.g, > > <ingress PE, ABR1> for domain 1, <ABR1, ABR2> for domain 2, etc. Now, in > this case, > > does <ingress PE, ABR1> itself again get a inter-domain path ? In theory, > yes. But in > > reality, it doesn't make sense. > > > Regards, > > PSF > > > Original > *From: *MarcelReuter(External) <marcel.reuter.external@telefonica.com> > *To: *pce@ietf.org <pce@ietf.org>; > *Date: *2023年09月15日 16:25 > *Subject: **[Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer Intra vs > Inter-domain* > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce > > Aloha, > > Dear colleagues, > > > > I have a question regarding the PCE with SR Flex-algo and multiple IGP > domains. > > > > In my understanding in each IGP Domain the Flex-Algo is calculated > independently of each other domain. > > The PCE should have the view of all IGP domains, including IGP metrics and > delay metrics. > > > > So if the PCE calculate a path and ingress and egress PE are in the same > IGP domain, > > It would be preferable to choose an IGP intra domain vs using another IGP > as transit. > > Or at least have the possibility to choose or prefer an Intra-Domain path > (with a flag maybe?) > > > > Reason: > > Especially in mobile operator RAN networks, there could be bandwidth > limitations in RAN IGP domains, but still a lower delay path. > > > > What’s your opinion about this? > > > > Thanks > > Marcel > > > > > > > > > > > > > > ------------------------------ > > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, > puede contener información privilegiada o confidencial y es para uso > exclusivo de la persona o entidad de destino. Si no es usted. el > destinatario indicado, queda notificado de que la lectura, utilización, > divulgación y/o copia sin autorización puede estar prohibida en virtud de > la legislación vigente. Si ha recibido este mensaje por error, le rogamos > que nos lo comunique inmediatamente por esta misma vía y proceda a su > destrucción. > > The information contained in this transmission is confidential and > privileged information intended only for the use of the individual or > entity named above. If the reader of this message is not the intended > recipient, you are hereby notified that any dissemination, distribution or > copying of this communication is strictly prohibited. If you have received > this transmission in error, do not read it. Please immediately reply to the > sender that you have received this communication in error and then delete > it. > > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, > pode conter informação privilegiada ou confidencial e é para uso exclusivo > da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário > indicado, fica notificado de que a leitura, utilização, divulgação e/ou > cópia sem autorização pode estar proibida em virtude da legislação vigente. > Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique > imediatamente por esta mesma via e proceda a sua destruição > > > _______________________________________________ > Pce mailing list > Pce@ietf.org > https://www.ietf.org/mailman/listinfo/pce >
- [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer Intr… Marcel Reuter (External)
- Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer … peng.shaofu
- Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer … Dhruv Dhody
- Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer … Samuel Sidor (ssidor)
- Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer … Dhruv Dhody
- Re: [Pce] [PCE]: Draft-ietf-pce-sid-algo: Prefer … Andrew Stone (Nokia)