IETF Logo Mail Archive

Re: [Apn] Apn Digest, Vol 23, Issue 1

Joel Halpern <jmh@joelhalpern.com> Mon, 23 January 2023 02:19 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C7E8C1516EB for <apn@ietfa.amsl.com>; Sun, 22 Jan 2023 18:19:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 (1024-bit key) header.d=joelhalpern.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 2cdLswR6W4TE for <apn@ietfa.amsl.com>; Sun, 22 Jan 2023 18:19:02 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 57A49C1516FF for <apn@ietf.org>; Sun, 22 Jan 2023 18:19:02 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4P0Ygp0zC3z1pZDg; Sun, 22 Jan 2023 18:19:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1674440342; bh=cC0k1tPbdQCuwPviAEp8u62PoWO//m4ps++TGslsMl8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=esD98kTWpvHWiQekXwLPtaWwjpBememQqLEdlRCTZHt1jOAFpc1fSkxsYU9OHugUO cLU2klUxOjXckugZkZj2B3HLciix9hb6avCcLp9sZFn8kg7ah2yyT5ZTDFEj/4l5Cm 1oVQfWBuuxIyWC9MajihKVhX9x58qu0wldBgGevE=
X-Quarantine-ID: <tI59Y5dL5lze>
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.21.74] (unknown [50.233.136.230]) (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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4P0Ygn3xhPz1pVyf; Sun, 22 Jan 2023 18:19:01 -0800 (PST)
Content-Type: multipart/alternative; boundary="------------E5YOeLpCkdRnEDxYMAyhNxqq"
Message-ID: <fbf65d89-a83d-644d-4def-44c402a65bb8@joelhalpern.com>
Date: Sun, 22 Jan 2023 21:19:00 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1
Content-Language: en-US
To: Lin He <helin1170@gmail.com>, apn@ietf.org
References: <mailman.1374.1674007488.24702.apn@ietf.org> <CABtDdH3g+ABwvtnt_+04H2X_4t0paCEbS-Cu1UyHaeLY0-Nu+Q@mail.gmail.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <CABtDdH3g+ABwvtnt_+04H2X_4t0paCEbS-Cu1UyHaeLY0-Nu+Q@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/Vc2M_yJFxtifzutM2tIz-4r2gOw>
Subject: Re: [Apn] Apn Digest, Vol 23, Issue 1
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Jan 2023 02:19:06 -0000

If you are doing this entirely inside your own network, NSH, with 
defined TLVs, can do what you describe.  It is specifically restricted 
to intra-domain usage.

Yours,

Joel

On 1/22/2023 8:48 PM, Lin He wrote:
> Hi, all.
>
> With multiple campuses connected to our national education network, 
> malicious traffic needs to be filtered in a timely manner. Once it is 
> found where the malicious traffic is coming from, it must be able to 
> be traced back to its source. However, once packets enter the network, 
> it isn't easy to know from which access edge they came. Therefore, it 
> would be good to have some mechanism to carry information, such as 
> access devices and interfaces. Since we will also be providing many 
> services in the network, it would be nice to have a common mechanism 
> for classifying traffic at the edge and in the network. The APN WG 
> seems like a good place to investigate potential solutions for our needs.
>
>
> Yours Sincerely,
>
> Lin He
>
>
>     ---------- Forwarded message ----------
>     From: Donald Eastlake <d3e3e3@gmail.com>
>     To: apn@ietf.org
>     Cc: apn-chairs@ietf.org
>     Bcc:
>     Date: Tue, 17 Jan 2023 21:04:28 -0500
>     Subject: [Apn] Further revised draft Charter
>     I've gotten some comments and I've re-read some of the AD
>     DISCUSSES and comments. Based on that I've updated the draft
>     Charter as attached.  Comments are welcome.
>
>     Thanks,
>     Donald
>     ===============================
>      Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>      2386 Panoramic Circle, Apopka, FL 32703 USA
>     d3e3e3@gmail.com
>     Apn mailing list
>     Apn@ietf.org
>     https://www.ietf.org/mailman/listinfo/apn
>
>

v2.23.0 | Report a Bug | By Email