Re: [Apn] [Network-tokens] [arch-d] Questions for APN: Q#6 and Q#7 Tue, 29 September 2020 21:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B19E63A0EBE; Tue, 29 Sep 2020 14:31:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 3jIXbFRaqj8m; Tue, 29 Sep 2020 14:31:44 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 05E6C3A11F0; Tue, 29 Sep 2020 14:31:43 -0700 (PDT)
Received: by with SMTP id g29so4990891pgl.2; Tue, 29 Sep 2020 14:31:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=oO0cj+ISEE/ENRdto0+8pNJ/OygXmRVUl8GQvDFrLbE=; b=ihmdv5ThLZJcB/p8KUu+EzqaCZAAqrq9VGVXpfsRGeeKCIQipZ6kFb3aQqU+eccoXr AVukqY47xi6/UzX/TWN6wX1LllUJs+QVredasqqV07pgAe7uSM35ah1FDL8dkkAnh9ta BnQJPa2NgfXq/xuh1PYRDo37Ytg+PIDZML7REtTUFbrGXiS+sZN/E+BdBONjZrCYg09M uU9n/Wii+WeyxJRXPpVJ6I673I7GzJJi58TvWq2UmyURCx9ZA9EXHnRfZO1BvKlIuOlv 9jCWmRjgoT99njsnru+QYZ5odOIuVm/Jy+cJA22T5DuKQR9J7DHGU65mnPxLx09JwAsY LN7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=oO0cj+ISEE/ENRdto0+8pNJ/OygXmRVUl8GQvDFrLbE=; b=nZiF6acDXCyYIGIvya8c+vrF642JVtz5nK63e3jEW01St1ksoQAP2v2AQHYkYoycEt 4hxZymUN0l9pErKi9w9um/aFGFTGsIsH3Qf1b1w6y9Lcvw3OJfkHFnPFts4UOISfuI83 zh6KEbDuvGJx9nb9HutlaeKySDmw03y4KSG1xGpS7tIk299bxV8nhVTnOEyDGn0+sa0C THtpalYSYvbT1vdebeT3cU5uZfqdOkQGYc4troUxdyBHVrde49wd9/fNuDxi0CmBJG3B R8x02+1qjCQEcZiaqtdlUtJ00O22aZlY79b4MAJSWGb8TClkqRWMJ+nIiX4isfRdGRUD Yacg==
X-Gm-Message-State: AOAM530GE9WmX+D0R0d6rK6VIK1VzjXZqI0OkNEI7b4l2mUZFNp1yFPF fc6sNENt4sviOGzEHVarCQM=
X-Google-Smtp-Source: ABdhPJzUBX+AMoODYjRgHavdwVvR2qb6maHO/fX9KeR7TLuxAaxXMlxlYU+aamiPXt+KkM+Tg0EFxQ==
X-Received: by 2002:a17:902:b203:b029:d2:1ebe:d80c with SMTP id t3-20020a170902b203b02900d21ebed80cmr6497112plr.18.1601415103222; Tue, 29 Sep 2020 14:31:43 -0700 (PDT)
Received: from [] ( []) by with ESMTPSA id f6sm6609786pfq.82.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Sep 2020 14:31:42 -0700 (PDT)
Sender: Tony Li <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_24116701-48D8-4864-9955-D25C79E18931"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Tue, 29 Sep 2020 14:31:38 -0700
In-Reply-To: <>
Cc: "" <>, "" <>, "" <>
To: "Pengshuping (Peng Shuping)" <>
References: <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Apn] [Network-tokens] [arch-d] Questions for APN: Q#6 and Q#7
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Sep 2020 21:31:46 -0000

Hi Shuping,

> <>
> Basically, the information carried in the IP layer is used for traffic steering policy selection within a limited APN network domain in order to guarantee the SLA requirements.

I’m a little unclear on what I’m reading, so please pardon some clarifying questions.

In this document, I’m seeing two options defined for use in IPv6 extension headers.

The application aware ID option appears to be up to 255 bytes long, variable length, and consists of three different structures.

How does the forwarding engine determine which structure is in use? Can this option appear multiple times in the header? 
Within each structure, the fields are variable length, but there appears to be no way to determine how long the fields are.

The service-para option appears to be a bit more structured.  Again, this appears to be variable length, up to 255 bytes.
Within the option, we have numerous subTLVs. What is the purpose of the RESERVED fields? If you’re trying to retain alignment,
didn’t that go out the window with a two byte option header?

Does the delay sub-TLV indicate the overall path delay? Or the per-hop delay?  If the full path delay, how does a router know
whether this has been satisfied?  Do systems along the path decrease this value as the packet is forwarded? How does a router
know how much to decrement?

Is 24 bits really necessary for the Delay Variation?  Is a jitter of 16s even meaningful?

The packet loss ratio is a 24 bit (presumably unsigned) value.  Is this an integer? Normally ratios are expressed as a relation between multiple
integers. What are the semantics here?

Have you computed the amount of overhead that you will be introducing? It appears to me that you could easily have 1000 bytes of overhead per packet.  What does 
this do to service provider bandwidth consumption? What does this do to the ‘low-latency’ service that you want to provide?