Yes I can. I have been working on the representation and have introduced a distinction between service parameters and attributes of the service. I will add the 802.1 as an attribute. On 2013-07-26, at 5:43 AM, Guy Roberts <Guy.Roberts@dante.net> wrote:
Hi John,
I think these are fine for the demo in Singapore.
Can we indicate in the SD somehow that the service is compliant with 802.1q or 802.1ad (for example)? This may help the user to know what service behaviour they can expect.
Guy
-----Original Message----- From: nsi-wg-bounces@ogf.org [mailto:nsi-wg-bounces@ogf.org] On Behalf Of John MacAuley Sent: 25 July 2013 18:19 To: nsi-wg@ogf.org Group Subject: [Nsi-wg] Service Description for ETS
Peoples,
I am preparing to make a service description for the Ethernet Transport Service (ETS) we are running on the A-GOLE. I need opinions on minimum, maximum, and default values for this service. Can you please provide feedback on the following:
1. serviceType == ETS.A-GOLE
2. reservation duration - minimum X and maximum Y (no default)
3. capacity - minimum X and maximum Y (no default)
4. directionality - values (Bidirectional, Unidirectional) with default Bidirectional
5. symmetricPath - values (TRUE, FALSE) with default FALSE
6. sourceSTP mandatory
7. destSTP mandatory
6. ero optional
7. mtu - minimum X, maximum Y, default Z
8. burstsize - minimum X, maximum Y, default Z
Have I missed anything?
Thank you, John _______________________________________________ nsi-wg mailing list nsi-wg@ogf.org https://www.ogf.org/mailman/listinfo/nsi-wg