Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

37. We also need more understanding of how APN is relevant in encrypted environments. #37

Open
APN-Github opened this issue Feb 9, 2022 · 0 comments

Comments

@APN-Github
Copy link
Contributor

The APN attribute is acquired based on the existing information in the packet header such as 5-tuple (might be 2-tuple in an encrypted environment) and QinQ (S-VLAN and C-VLAN) at the edge devices of the APN domain, added to the data packets along with the tunnel encapsulation. This means that APN does not need to rely on the encrypted payload of the packet. Moreover, in this draft https://datatracker.ietf.org/doc/html/draft-li-apn-framework-04#section-5.1, we have also listed the APN Attribute Conveying Requirements, the [REQ 1d] is that “APN ID MUST be acquired from the existing available information of the packet header without interference into the payload.”

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant