I found these in one of Jerry's e-mail… ----- seviceTypeIdentifier "EFTS" <comment> This is the Common Service Definition file that defines all parameters associated with the Ethernet Framed Transport Service. <\comment> <attribute> <attrName>Capacity</attrName> <comment> Capacity is defined to be the average quantity of data that will be guaranteed to be transported per unit time from ingress to egress, normalized to 1 second. For example: 8 Mbps = 8x2^20 bits per second. The "Capacity" for the EFTS instance includes the ethernet frame header(s) but does not include sync bits or any inter-frame gap considerations. Further, the EFTS "Capacity" attribute does not include any additional headers that may be applied in transit. </comment> <attrPresence>required</attrPresence> --- May be "required" or "optional" <attrValue> <attrValueFloor 0 /> <attrValueCeiling 100,000,000,000 /> <attrValueUnits "bps /> <attrDefault> 0 </attrDefault> </attrValue> </attribute> <attribute> <attrName>BurstCharacteristics</attrName> <comment> BurstCharacteristics describes the maximum amount of data that the ingress STP will accept in a single sequence of packets at line rate of that STP. Bursts must be separated by a long enough quiescent period for the average long term rate of data transfer is within the capacity limits. Packets exceeding this burst profile are policed and will be immediately dropped when detected. </comment> <attrPresence>required</attrPresence> --- May be "required" or "optional" <attrValue> <attrValueFloor 0 /> <attrValueCeiling 100,000,000,000 /> <attrValueUnits "bytes /> <attrDefault> 9000 </attrDefault> </attrValue> </attribute> <attribute> <attrName>Directionality</attrName> <comment> Directionality specifies whether the Connect requested is to be a "unidirectional" or "bidirectional" circuit. The implications for unidirectional are fairly obvious. However for bidirectional connections the STPs must be defined as bi-directional. Note: there may be ambiguity in certain topological scenarios where the routing of the connection may not be clear. </comment> <attrPresence>required</attrPresence> --- May be "required" or "optional" <attrValue> <attrValueChoice "unidirectional" /> <attrValueChoice "bidirectional" /> <attrDefault> "unidirectional" </attrDefault> </attrValue> </attribute> --- On 2013-07-25, at 1:19 PM, John MacAuley <john.macauley@surfnet.nl> wrote:

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