Re: [STDS-802-16] Resolution of comment 332
BTW, the .16e draft does not clearly specify how control plane
'broadcasted' IP packets are to be handled. For example, how will MIP
agent advertisements or IPv6 prefix advertisements be handled -
delivered on the secondary management CID or broadcast CID or something
else. ICMP routing related updates are another example. Many of these
affect timing especially in the context of handovers and the ability for
an MSS to transmit/receive data immediately after a handover or in
steady state. If this is described somewhere, can someone send me a
pointer. If not, it needs to be addressed via comments.
-Prakash
-----Original Message-----
From: owner-stds-802-16@LISTSERV.IEEE.ORG
[mailto:owner-stds-802-16@LISTSERV.IEEE.ORG] On Behalf Of Jeff Mandin
Sent: Monday, May 03, 2004 4:26 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] Resolution of comment 332
> My understanding of Secondary Management connection role is to carry
>traffic from / to the SS itself.
>particularly, this traffic does not pass CS SAP, but rather goes from /
>to Management Entities [Fig. 1]
>
>Vladimir
>
>
>
That's really the crux of the issue! IP is an "internetwork protocol",
and includes the notion of an "IP interface", which is inevitably
associated with a MAC SAP.
So SNMP etc. traffic should really be viewed as application traffic (ie.
which passes the CS SAP).
Indeed, many people's conception is that the management traffic
originates at an NMS external to the BS which is then bridged or routed.
If so, then the traffic certainly passes the CS SAP. For external
traffic to not pass the CS SAP, we would require a management proxy
entity.