Re: [ippm] Fwd: New Version Notification for draft-mirsky-mpls-stamp-00.txt

Greg Mirsky <gregimirsky@gmail.com> Fri, 29 July 2022 15:14 UTC

MIME-Version: 1.0
References: <165906234425.8931.3605791496514833693@ietfa.amsl.com> <CA+RyBmXPnTAM=pYJqsV6R--0BqyNgpVVQuqzxQkP=6U-XV4RBA@mail.gmail.com> <DM5PR0801MB37818DA6568342745080B5A18B999@DM5PR0801MB3781.namprd08.prod.outlook.com>
In-Reply-To: <DM5PR0801MB37818DA6568342745080B5A18B999@DM5PR0801MB3781.namprd08.prod.outlook.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 29 Jul 2022 11:13:56 -0400
Message-ID: <CA+RyBmW2y21j4pwJg+6rQBZ5btWUN9VF9QPPiQuOH93U9J3KQQ@mail.gmail.com>
To: "Foote, Footer (Nokia - CA)" <footer.foote@nokia.com>
Cc: mpls <mpls@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000000cc9405e4f31a3a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/gr18bBdPqhZ4zakgCXNP4Jjyy94>
Subject: Re: [ippm] Fwd: New Version Notification for draft-mirsky-mpls-stamp-00.txt
Precedence: list

Hi Footer,
indeed, thank you for catching that. Will fix it in the next version.

Regards,
Greg

On Fri, Jul 29, 2022 at 11:07 AM Foote, Footer (Nokia - CA) <
footer.foote@nokia.com> wrote:

> Hi Greg.
>
>
>
> I think there is one small typo in the draft.
>
>
>
> The STAMP test packet sent by the ingress LSR SHOULD be a UDP packet with
> a well-known destination port 672 [RFC8762] and a source port assigned by
> the sender.
>
>
>
> I think the well-known destination port should be 862.
>
>
>
> Footer
>
>
>
>
>
> *From:* ippm <ippm-bounces@ietf.org> *On Behalf Of * Greg Mirsky
> *Sent:* Thursday, 28 July 2022 22:44
> *To:* mpls <mpls@ietf.org>; IETF IPPM WG <ippm@ietf.org>
> *Subject:* [ippm] Fwd: New Version Notification for
> draft-mirsky-mpls-stamp-00.txt
>
>
>
> Dear All,
>
> the new draft describes IP/UDP encapsulation of the Simple Two-Active
> Measurement Protocol and the use of the MPLS LSP Ping to bootstrap a STAMP
> test session using the Reflected Packet Path TLV. Optionally, the Reflected
> PAcket Path TLV can be used to instruct the STAMP Session-Reflector to use
> the specified FEC or Non-FEC (for SR-MPLS) route.
>
> Always welcome your comments, questions, and suggestions.
>
>
>
> Regards,
>
> Greg
>
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: Thu, Jul 28, 2022 at 10:39 PM
> Subject: New Version Notification for draft-mirsky-mpls-stamp-00.txt
> To: Greg Mirsky <gregimirsky@gmail.com>
>
>
>
>
> A new version of I-D, draft-mirsky-mpls-stamp-00.txt
> has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> Name:           draft-mirsky-mpls-stamp
> Revision:       00
> Title:          Simple Two-way Active Measurement Protocol (STAMP) for
> MPLS Label Switched Paths (LSPs)
> Document date:  2022-07-28
> Group:          Individual Submission
> Pages:          8
> URL:
> https://www.ietf.org/archive/id/draft-mirsky-mpls-stamp-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-mirsky-mpls-stamp/
> Html:
> https://www.ietf.org/archive/id/draft-mirsky-mpls-stamp-00.html
> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-mirsky-mpls-stamp
>
>
> Abstract:
>    Simple Two-way Active Measurement Protocol (STAMP), defined in RFC
>    8762 and RFC 8972, is expected to be able to monitor the performance
>    of paths between systems that use a wide variety of encapsulations.
>    This document defines encapsulation and bootstrapping of a STAMP test
>    session over an MPLS Label Switched Path.
>
>
>
>
> The IETF Secretariat
>
>

[ippm] Fwd: New Version Notification for draft-mi… Greg Mirsky
Re: [ippm] Fwd: New Version Notification for draf… Foote, Footer (Nokia - CA)
Re: [ippm] Fwd: New Version Notification for draf… Greg Mirsky