IETF Logo Mail Archive

[Teas] Re: [mpls] Re: Comments abount rfc2205 Resource ReSerVation Protocol (RSVP)

Tarek Saad <tsaad.net@gmail.com> Tue, 22 October 2024 15:35 UTC

Return-Path: <tsaad.net@gmail.com>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56D01C18DB92; Tue, 22 Oct 2024 08:35:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 ky_SPUXWuBrE; Tue, 22 Oct 2024 08:35:30 -0700 (PDT)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 A1606C169438; Tue, 22 Oct 2024 08:35:30 -0700 (PDT)
Received: by mail-qv1-xf2b.google.com with SMTP id 6a1803df08f44-6cbd12b38b4so37123316d6.2; Tue, 22 Oct 2024 08:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729611330; x=1730216130; darn=ietf.org; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=Jj032I3wCVIGtKBQO7n8eoxkZSZKFt74uvQhs26rr6M=; b=KJrRVDfibXlBeqOpTDR60RjxA9MbNhwrZEhddCRn/oLMjFFlqwbQvk2f02jgPdz/BR GR+1bY/wVUN6bIU7C2lRaBtY9qVGstTthmrkj+nuabtSt2Pl8kZm59IpwBBz1uyrmpzU tpygJj1Pbt7cXsl9IrLdGduUHISRD4N04/0h9WtcDv474I5uWEYBc/SKALNeQ5+2szUi eKCWbl6eyJ6S+6Q3rC263xRkX4Ww0X33gNRIIe2DqeacPUKJL8TrE3NV0pIASnEtYnJQ KYVdZwH4CZOYRSP5gqjPyLiPF0hoKEj+AVBFSHwwn1Q8/vAIUhWe1vt29RsM6R5N0J0Y LrvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729611330; x=1730216130; h=mime-version:content-language:accept-language:in-reply-to :references:message-id:date:thread-index:thread-topic:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Jj032I3wCVIGtKBQO7n8eoxkZSZKFt74uvQhs26rr6M=; b=h24FYmQaHsdr2GXN2LvZHwZvmJ6p38Lu4kNlXfOEw6GyUHJXrNaKiRwXjYcYYaPPiv qwMo4E8GF+G6rDE9qNNE+L8sqFM7940DdHdemQFzOh0UlJwO84zh5ODdlAZXdQBurzOA Ev1PbaNOzTNowbFB9BWjYTCH38zeKcqRE+kYYrc/Z1kJak8xvKcfLrcUYkbYeKbzOKID VwiG7j63QSpuVFnHZ8eX8pEEjTqj0QGFSZ829eXW6jQxd6Ov6hh7BYnYnCMEh56+Z6Lj B6+eoqDUJQAAQkVRZ6AO3taOfo0SD1EOAtZvIB1trs9Z0kBMAkJBBrAbyINm/kS/tfvL yKqA==
X-Forwarded-Encrypted: i=1; AJvYcCV4KRpoE5om1TSSkLifF9C6bNBtgPv6Ksz2jBPyjedEMcUsKXZZ4j8Th9wwiwr+9aWNbO4b@ietf.org
X-Gm-Message-State: AOJu0Yyb/59ZdtL1awZGg/aYCcessKYA7gWTSmQt4NYxZi/RMRO5tUnc uxc4KAm83bztkk22ob/sypAwQNBPDc6zJeUjTT37zo341It2FnQP
X-Google-Smtp-Source: AGHT+IEI2epYk7NJ7kf+PBktXxE3mZ3cXZgbu1q3qL+e4m8/QkRXZYN1tSuy8ASd8R3BMeJ4SPD7Nw==
X-Received: by 2002:a05:6214:4a8f:b0:6cc:37bb:40b with SMTP id 6a1803df08f44-6cde15dedbbmr315461196d6.37.1729611329586; Tue, 22 Oct 2024 08:35:29 -0700 (PDT)
Received: from MN0P220MB1924.NAMP220.PROD.OUTLOOK.COM ([2603:1036:207:43d::5]) by smtp.gmail.com with ESMTPSA id 6a1803df08f44-6ce00999a91sm29563006d6.88.2024.10.22.08.35.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 22 Oct 2024 08:35:29 -0700 (PDT)
From: Tarek Saad <tsaad.net@gmail.com>
To: Tony Li <tony.li@tony.li>, Tuấn Anh Vũ <anhvt.hdg@gmail.com>, TEAS WG <teas@ietf.org>
Thread-Topic: [mpls] Re: Comments abount rfc2205 Resource ReSerVation Protocol (RSVP)
Thread-Index: AQHbJEUcwQgxmveB50y5jul4GCQSXrKS5j/D
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Tue, 22 Oct 2024 15:35:28 +0000
Message-ID: <MN0P220MB19242FA7DEF27643CA9EEF2BFC4C2@MN0P220MB1924.NAMP220.PROD.OUTLOOK.COM>
References: <CA+SXWCnrL-0AbHKJo_k0RNhVP-maJQqkwfdaZfx4wo82eKYO=w@mail.gmail.com> <28003919-0AF7-495E-A5B4-8CE3A7F7C608@tony.li>
In-Reply-To: <28003919-0AF7-495E-A5B4-8CE3A7F7C608@tony.li>
Accept-Language: en-US
Content-Language: en-CA
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator:
X-MS-Exchange-Organization-RecordReviewCfmType: 0
x-ms-reactions: allow
Content-Type: multipart/alternative; boundary="_000_MN0P220MB19242FA7DEF27643CA9EEF2BFC4C2MN0P220MB1924NAMP_"
MIME-Version: 1.0
Message-ID-Hash: NQCF6XRMQGNHUQCCRTEHIUN64T7PUWIQ
X-Message-ID-Hash: NQCF6XRMQGNHUQCCRTEHIUN64T7PUWIQ
X-MailFrom: tsaad.net@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-teas.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: mpls <mpls@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Teas] Re: [mpls] Re: Comments abount rfc2205 Resource ReSerVation Protocol (RSVP)
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/UfFA22FpsdpGcJSeErFYA3N201w>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Owner: <mailto:teas-owner@ietf.org>
List-Post: <mailto:teas@ietf.org>
List-Subscribe: <mailto:teas-join@ietf.org>
List-Unsubscribe: <mailto:teas-leave@ietf.org>

Thanks Tony. Added teas alias.

Hi AnhVT,

RSVP PathErr can be used to propagate errors upstream – there’s Path_State_Removed that RFC3473 introduced to also notify that state has been removed. Does that address your need?

Regards,
Tarek

From: Tony Li <tony1athome@gmail.com> on behalf of Tony Li <tony.li@tony.li>
Date: Tuesday, October 22, 2024 at 1:41 AM
To: Tuấn Anh Vũ <anhvt.hdg@gmail.com>
Cc: mpls <mpls@ietf.org>
Subject: [mpls] Re: Comments abount rfc2205 Resource ReSerVation Protocol (RSVP)

[WG chair hat: on]

Hi AnhVT,

This probably would be more approrpiate if directed to the TEAS WG.  They are responsible for RSVP maintenance.

Regards,
Tony



On Oct 21, 2024, at 8:44 PM, Tuấn Anh Vũ - anhvt.hdg at gmail.com <mailforwards@cloudmails.net> wrote:

Hi IETF team,
I'm AnhVT from the SVTech company in VietNam, I have experienced some RSVP issues in the IPv4 MPLS network.
I suspect that RSVP has a point that needs to be enhanced. I describe this point below:

I./ Topology:
    ---------LSP-------->
    R1----R2----R3-----R4
          |    /
          |  /
           R5
II./ Issue
1./ Because of some bugs (exp: R3 experiences a flap link between R3-R2, but R2 does not recognize the interface flap), R3 indicates that LSP is down, then it deletes the LSP state and sends the PathTear downstream to R4.
2./Because R2 does not recognize the interface flap, R2 still keeps it available. It does not know that the LSP should be deleted.
3./ Due to 1./ and 2./ R1 does not know that the LSP is stuck because R3 and R4 deleted the LSP state, and R1 continues forwarding traffic to the LSP, This makes the service down.

III./ My comment
I think that RSVP needs a mechanic so that R3 signals to R2 to ensure that R2 knows that R3 deleted the LSP. Based on that signal, R2 will bring down the LSP and continue to send Reserve Tear to R1.

I hope that you take a look at my comment.

Regards,
AnhVT
_______________________________________________
mpls mailing list -- mpls@ietf.org
To unsubscribe send an email to mpls-leave@ietf.org

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