public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sivaraman Nainar via groups.io" <sivaramann=ami.com@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Maciej Rabeda <maciej.rabeda@linux.intel.com>
Cc: "Santhosh Kumar V" <santhoshkumarv@ami.com>,
	"Mike Su (蘇得緣)" <MikeSu@ami.com>,
	"Dhanaraj V" <vdhanaraj@ami.com>
Subject: [edk2-devel] reg: Two IAID assignment for single MAC Address
Date: Tue, 3 Oct 2023 17:08:38 +0000	[thread overview]
Message-ID: <BN0PR10MB498171FCC18D3CF239762B9FC2C4A@BN0PR10MB4981.namprd10.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]

Hello Maciej:

When IPV6 PXE Boot performed in the environment where client and server are connected behind Routers, there are two SARR process happens, and both are using different IAID’s.

During the PXE Boot IPV6, SARR Process Initiated to get the Boot File information. During that time one IAID Created (ff76fdbd). PxeBcCreateIp6Children()
During the Router Advertisement , SARR Process Initiated to get the Boot File. Ip6ConfigInitInstance()

Besides, according to the definition of IA(RFC-3315<https://datatracker.ietf.org/doc/html/rfc3315>):

An "identity-association" (IA) is a construct through which a server
and a client can identify, group, and manage a set of related IPv6
addresses. Each IA consists of an IAID and associated configuration
information.

A client must associate at least one distinct IA with each of its
network interfaces for which it is to request the assignment of IPv6
addresses from a DHCP server. The client uses the IAs assigned to an
interface to obtain configuration information from a server for that
interface. Each IA must be associated with exactly one interface.

But as per EDK2 Network Implementation it defines two IA IDs for same client.  Is there any reasoning behind this implementation?

What if both the process uses Same IAID?

Thanks
Siva
-The information contained in this message may be confidential and proprietary to American Megatrends (AMI). This communication is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. Please promptly notify the sender by reply e-mail or by telephone at 770-246-8600, and then delete or destroy all copies of the transmission.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#109296): https://edk2.groups.io/g/devel/message/109296
Mute This Topic: https://groups.io/mt/101738223/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 6059 bytes --]

             reply	other threads:[~2023-10-03 17:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-03 17:08 Sivaraman Nainar via groups.io [this message]
2023-10-03 17:48 ` [edk2-devel] reg: Two IAID assignment for single MAC Address Sivaraman Nainar via groups.io
2023-10-04 21:53   ` Clark-williams, Zachary
2023-10-05  5:38     ` Sivaraman Nainar via groups.io
2023-10-12 12:26       ` Sivaraman Nainar via groups.io
2023-11-03  4:50         ` Sivaraman Nainar via groups.io

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN0PR10MB498171FCC18D3CF239762B9FC2C4A@BN0PR10MB4981.namprd10.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox