On 6/28/12 10:47 AM, thus spake Jeroen van der Ham:
On 28 Jun 2012, at 16:17, Jason Zurawski wrote:
Option 2 is how OSCARS currently works today, and I believe it works well. I would vote to go with that for 'ease of implementation' :)
Good to hear! Can you describe the syntax constraints that OSCARS uses?
What do I look like, a programmer :) Aaron or Andy may be able to. I believe the comma and dash are popular and expected as I look at examples:
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
-jason
On Jun 28, 2012, at 10:55 AM, Jason Zurawski wrote:
On 6/28/12 10:47 AM, thus spake Jeroen van der Ham:
On 28 Jun 2012, at 16:17, Jason Zurawski wrote:
Option 2 is how OSCARS currently works today, and I believe it works well. I would vote to go with that for 'ease of implementation' :)
Good to hear! Can you describe the syntax constraints that OSCARS uses?
What do I look like, a programmer :)
Aaron or Andy may be able to. I believe the comma and dash are popular and expected as I look at examples:
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
Dashes and commas are the only special characters that OSCARS allows. A dash in between two numbers to represent a continuous range (e.g. 3000-4000). It requires the left number to be less than the second number. Discontinuous ranges can be separated by commas (3000-3250,3500,3750-4000). Its pretty easy to parse, generally we do a couple splits on commas and dashes. Andy
-jason
Hi, On 28 Jun 2012, at 17:11, Andrew Lake wrote:
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
Dashes and commas are the only special characters that OSCARS allows. A dash in between two numbers to represent a continuous range (e.g. 3000-4000). It requires the left number to be less than the second number. Discontinuous ranges can be separated by commas (3000-3250,3500,3750-4000). Its pretty easy to parse, generally we do a couple splits on commas and dashes.
Thanks, that does sound easy enough. I assume those ranges are inclusive? Jeroen.
On Jun 28, 2012, at 11:21 AM, Jeroen van der Ham wrote:
Hi,
On 28 Jun 2012, at 17:11, Andrew Lake wrote:
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
Dashes and commas are the only special characters that OSCARS allows. A dash in between two numbers to represent a continuous range (e.g. 3000-4000). It requires the left number to be less than the second number. Discontinuous ranges can be separated by commas (3000-3250,3500,3750-4000). Its pretty easy to parse, generally we do a couple splits on commas and dashes.
Thanks, that does sound easy enough. I assume those ranges are inclusive?
Yes, they are inclusive. Andy
Jeroen.
Hey Andrew,
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
[..] Discontinuous ranges can be separated by commas (3000-3250,3500,3750-4000). Its pretty easy to parse, generally we do a couple splits on commas and dashes.
Thanks. This indeed is easy enough, so let's go for this option.
Dashes and commas are the only special characters that OSCARS allows.
This disallows negative numbers. Paranoid sanity check: would there ever be a technology that allows negative numbers as labels? The only thing I can imagine if one would describe the central frequency of G.694.1 (DWDM) as "0", positive numbers for frequencies above 193.1 THz (thus wavelengths below 1552.52 nm), and negative numbers for frequencies below 193.1 THz (wavelengths above 1552.52 nm). I don't think this is an issue -- it is easy enough to use wavelength or frequency to avoid negative numbers, and GMPLS also does not list any negative label at http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig-parameters.xm.... Proposal 2-bis: =============== * Use the syntax with dashes and commas as described in proposal 2. * Explicitly forbid negative labels to avoid parsing errors later. OK? Freek
ACK -jason On 6/28/12 12:06 PM, thus spake Freek Dijkstra:
Hey Andrew,
<vlanRangeAvailability>3800-3809</vlanRangeAvailability>
[..] Discontinuous ranges can be separated by commas (3000-3250,3500,3750-4000). Its pretty easy to parse, generally we do a couple splits on commas and dashes.
Thanks. This indeed is easy enough, so let's go for this option.
Dashes and commas are the only special characters that OSCARS allows.
This disallows negative numbers.
Paranoid sanity check: would there ever be a technology that allows negative numbers as labels?
The only thing I can imagine if one would describe the central frequency of G.694.1 (DWDM) as "0", positive numbers for frequencies above 193.1 THz (thus wavelengths below 1552.52 nm), and negative numbers for frequencies below 193.1 THz (wavelengths above 1552.52 nm).
I don't think this is an issue -- it is easy enough to use wavelength or frequency to avoid negative numbers, and GMPLS also does not list any negative label at http://www.iana.org/assignments/gmpls-sig-parameters/gmpls-sig-parameters.xm....
Proposal 2-bis: =============== * Use the syntax with dashes and commas as described in proposal 2. * Explicitly forbid negative labels to avoid parsing errors later.
OK?
Freek
participants (4)
-
Andrew Lake -
Freek Dijkstra -
Jason Zurawski -
Jeroen van der Ham