IETF Logo Mail Archive

[Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)

Acee Lindem <acee.ietf@gmail.com> Wed, 07 August 2024 12:28 UTC

Return-Path: <acee.ietf@gmail.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 9CDFEC14F69E for <idr@ietfa.amsl.com>; Wed, 7 Aug 2024 05:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.095
X-Spam-Level:
X-Spam-Status: No, score=-6.095 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, 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=gmail.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 FdosTVBmYqTr for <idr@ietfa.amsl.com>; Wed, 7 Aug 2024 05:28:27 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22B6C14F5EC for <idr@ietf.org>; Wed, 7 Aug 2024 05:28:27 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id af79cd13be357-7a3375015f8so88170385a.1 for <idr@ietf.org>; Wed, 07 Aug 2024 05:28:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723033707; x=1723638507; darn=ietf.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=T83zyOIi4HhBh3a4Wz+0DSVF6NgevoxKZ2bdAP8otco=; b=lG1MWk2XSou4pBJde+HgqkLA46lvezpIed/NP9830vTSh0l7AKhOAkYF9JgRKPmIYy IxAdjwGpGbF7Q5jlY1wOatfIF8N0tAb8EeYWyzEB/2qjqp4xIRts2pYNSDqFS+SAoi1k KMSQmZYSUMxg9pL2J/kedHJrm3yEZahk+LaVhGoYY9T8+ui5F9fLoPdla4xAtUUBded8 xnv7hP9Ccc60UVPF3quz4KpWe5t7lOnnzVsrJ9N1J8Zvq7QzO6a0g0LOcdqkjLkUZ3x+ JnDvMSvrg0i6AUHx0BrN/faJHIxPBmvzsMnqjTUUQ/dRN2z+9WtE+KNbzGHkdXW5tsBw E0oA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723033707; x=1723638507; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=T83zyOIi4HhBh3a4Wz+0DSVF6NgevoxKZ2bdAP8otco=; b=UoLFDOUSXYZK3nkFUIJ+d/xiifcB02zsYtuwXi008vDzY5LmxOqOTKDEX8kkcPuws0 C8X/Eiakk/Ze8faoA+u9x63PH7c6xvQJppaXB+trOns3v5iflnGZ/kPwlZsWaVxfQ2TL zLqG6sD4VkBl7Hrbjd5mw2ptJuHpJfgKfHlWz41KBaibyTBUsohhnEEyMKipnLF17ts/ 19a0uXWiCYZ4DXa28xvzrOkXCFPYngBiTasom716KQDumxs5HsLIpq++5l2ey04pMExv jDyCGUUXIG3hpDtRGvCidNdGQtV9JIBwU3ZQjQmPyYdE9JW13CUoyz2k3A7ixYOnNbAb MM1g==
X-Forwarded-Encrypted: i=1; AJvYcCWL4ke1ptXhpxOIKsVWjXxWwxzDYNWCLMAnlWpFA/4Wa6dCqKpVW9I2XUYlXgmNF93htaa6ILrF2ftlv70=
X-Gm-Message-State: AOJu0YwCiEZZ2KuD9ya8mSlL/2CzMzGNpTFkLb5pjHZZcK7oA8tFw7Gn RMky7rABDsaeduhaJMVPRfhuowuG5wRBGwT8WB+4VC2jPT3B0DGq
X-Google-Smtp-Source: AGHT+IG5Rw7vqCm3PyNT1OF8rLIBWfHGyeTwUtoAbzP8pdyjWrOeX3J19he9vhpJQBZ0yidiBhWX0A==
X-Received: by 2002:a05:620a:2482:b0:7a2:e53:3f58 with SMTP id af79cd13be357-7a34ef0acf2mr2288603285a.25.1723033706372; Wed, 07 Aug 2024 05:28:26 -0700 (PDT)
Received: from smtpclient.apple ([136.54.28.118]) by smtp.gmail.com with ESMTPSA id af79cd13be357-7a3786b5a15sm54001285a.101.2024.08.07.05.28.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Aug 2024 05:28:26 -0700 (PDT)
From: Acee Lindem <acee.ietf@gmail.com>
Message-Id: <77373FCC-E596-4295-B066-DC45B140302E@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EF938160-78D1-450F-BD19-FDEB665E94DB"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Wed, 07 Aug 2024 08:28:15 -0400
In-Reply-To: <SY8P282MB4885F8EF2E6BE5376C4726A7FCBF2@SY8P282MB4885.AUSP282.PROD.OUTLOOK.COM>
To: li_zhenqiang@hotmail.com
References: <SJ0PR08MB66220668F30E8B89E4C697C2B3B32@SJ0PR08MB6622.namprd08.prod.outlook.com> <SY8P282MB4885F8EF2E6BE5376C4726A7FCBF2@SY8P282MB4885.AUSP282.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: LA72CWVFVKISBDYUNONFDH2LO5J7QDG5
X-Message-ID-Hash: LA72CWVFVKISBDYUNONFDH2LO5J7QDG5
X-MailFrom: acee.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-idr.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Idr] Re: WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
List-Id: Inter-Domain Routing <idr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/0nzWn46s0K2WuiviXJojCTTuzfA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Owner: <mailto:idr-owner@ietf.org>
List-Post: <mailto:idr@ietf.org>
List-Subscribe: <mailto:idr-join@ietf.org>
List-Unsubscribe: <mailto:idr-leave@ietf.org>

As a contributor and implementor of RFC 9086, I support adoption. I agree with Zhenqiang’s responses - this document on its own doesn’t provide protection from BUM traffic looping. 


Thanks,
Acee

> On Aug 6, 2024, at 05:15, li_zhenqiang@hotmail.com wrote:
> 
> Hello Sue and all,
> 
> As a coauthor I support the adoption of this draft and I don't know any IPR that may relate to it.
> 
> Does this BGP-LS addition help SR Egress Peering points in operational networks?  
> Yes.
> 
> Does this draft handle the BUM traffic in a way that Prevents looping?(Broadcast, Unknown Unicast, and Multicast (BUM))
> No. This dfaft defines no new method for loop preventing  because  existing mechanisms work for L2bundle.
> 
> Are there any problems in the technology described?
> No.
> 
> Best Regards,
> Zhenqiang Li
> China Mobile
> li_zhenqiang@hotmail.com <mailto:li_zhenqiang@hotmail.com>
>  
> From: Susan Hares <mailto:shares@ndzh.com>
> Date: 2024-08-02 22:11
> To: idr@ietf.org <mailto:idr@ietf.org>
> Subject: [Idr] WG adoption call for draft-lin-idr-sr-epe-over-l2bundle-07 (8/2 to 8/16)
> IDR WG: 
>  
> This begins a 2 week WG adoption call for  
> draft-lin-idr-sr-epe-over-l2bundle-07.txt
> https://datatracker.ietf.org/doc/draft-lin-idr-sr-epe-over-l2bundle/
>  
>  
> The authors should reply to this email with an
> IPR statement indicating whether they know of an intellectual property.
>  
> This document describes how to support Segment Routing
> BGP Egress Peer Engineering over Layer 2 bundle members.
> This document updates [RFC9085] to allow the L2 Bundle Member
> Attributes TLV to be added to the BGP-LS Attribute
> associated with the Link NLRI of BGP peering link.
>  
>  
> In your comments regarding adoption,  please consider
>  
> Does this BGP-LS addition help SR Egress Peering points
> in operational networks?  
> Does this draft handle the BUM traffic in a way that
> Prevents looping?
> (Broadcast, Unknown Unicast, and Multicast (BUM))
> Are there any problems in the technology described?
>  
> Cheerily, Sue Hares 
> _______________________________________________
> Idr mailing list -- idr@ietf.org <mailto:idr@ietf.org>
> To unsubscribe send an email to idr-leave@ietf.org <mailto:idr-leave@ietf.org>

v2.26.15 | Report a Bug | By Email | System Status