Why we need two seperate tables for inbound and outbound in draft-ietf-pwe3-pw-atm-mib-05.txt

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Why we need two seperate tables for inbound and outbound in draft-ietf-pwe3-pw-atm-mib-05.txt

From: "Murugesan Ramalingam" <murugu08 at gmail.com>
To: Ietf at ietf.org
Date: Fri, 11 Jul 2008 15:51:28 +0530

Hi All,
    I  have a query in the draft Managed Objects for ATM over
Packet Switched Network  (draft-ietf-pwe3-pw-atm-mib-05.txt) that why
there are seperate tables for Inbound (pwAtmInboundNto1Table) and
Outbound (pwAtmOutboundNto1Table). Is there any specific reason to
have this, please let me know.


Thanks & Regards,
Murugesan R
_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www.ietf.org/mailman/listinfo/ietf

Prev by Date: Weekly posting summary for ietf at ietf.org
Next by Date: Re: Call for review of proposed update to ID-Checklist
Previous by thread: Upcoming Jabber Server Load Test
Next by thread: New IETF Journal available now (Volume 4, Issue 1)
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Why we need two seperate tables for inbound and outbound in draft-ietf-pwe3-pw-atm-mib-05.txt

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.