January 2014 - Nsi-wg - lists.ogf.org

Fwd: Reminder to ReadyTalk Users: Use VoIP
by Inder Monga 22 Jan '14

22 Jan '14

FYI - an internal notice of the ability to use VOIP with readytalk bridge that we use for NSI calls. This should help if you are traveling and have IP connectivity. Inder From: ReadyTalk on Behalf of ECS <kim.morse(a)readytalk.com> Date: Tue, Jan 21, 2014 at 12:40 PM Subject: Reminder to ReadyTalk Users: Use VoIP To: imonga(a)es.net If you have trouble viewing this email, read the online version<http://s1904.t.en25.com/e/es.aspx?s=1904&e=68405&elq=e8c1825e990042bcaabfb7…>. <http://s1904.t.en25.com/e/er?s=1904&lid=38&elq=e8c1825e990042bcaabfb7ee5cda…> <http://s1904.t.en25.com/e/er?s=1904&lid=11&elq=e8c1825e990042bcaabfb7ee5cda…> <http://s1904.t.en25.com/e/er?s=1904&lid=2786&elq=e8c1825e990042bcaabfb7ee5c…> <http://s1904.t.en25.com/e/er?s=1904&lid=41&elq=e8c1825e990042bcaabfb7ee5cda…> Dear Inder , As a valued customer of our ReadyTalk service we would like to remind about a new feature recently released by ReadyTalk – VoIP audio conferencing. As an ECS ReadyTalk user hosting a number of conferences with International participants, you can help us manage costs by using ReadyTalk’s VOIP feature. Rather than call into meetings using your telephone, you can simply initiate ReadyTalk VOIP services in the web interface and use your computer speakers and microphone for the audio portion of your conference. Using VOIP will significantly reduce the conference call costs. International conferencing is one of the fastest growing segments of this collaboration service and we are seeing increasing international connection costs. Here is some quick guidance on how to use ReadyTalk VOIP: - As a meeting host, log into your ReadyTalk Conference Controls and click the ‘Use Computer’ option on the left side under ‘Audio Controls’. From the Mic and Speaker dialog box, select your hardware from the drop down menu. - Meeting participants will have the option to join with a VoIP connection directly from their participant application, once the host has started the meeting. - Hosts should instruct participants to select the Audio button at the top of the participant window. Select Use your Computer Mic and Speaker option. Select their available microphone and they will automatically join the audio meeting from their PC. - As with any form of conference calling you should instruct your participants to mute their microphones if they are not speaking. - For optimal audio quality, we recommend that individuals utilizing VoIP use a headset that is plugged in via their USB port. On your next International call try the new VOIP feature and please ask your participants to try the new VOIP feature as well. Let us know how well the VOIP services worked for your conference by sending email to ecs-admin(a)es.net. Thank you. Sincerely, ECS ReadyTalk Team To unsubscribe from future emails or to update your email preferences click here<http://meet.readytalk.com/content/PrefCenter?elq=e8c1825e990042bcaabfb7ee5c…>. ReadyTalk | 1900 Sixteenth Street | Denver, Colorado 80202 800.843.9166 Privacy Policy<http://www.readytalk.com/about/privacy-policy.php?elq=e8c1825e990042bcaabfb…>

1 0

NSI CS v2.0 available for public comment
by Guy Roberts 20 Jan '14

20 Jan '14

Hello all, The NSI CS v2.0 document was posted for 60 day public comment on Friday 17th January. You can view the document and post your comments here: http://redmine.ogf.org/projects/editor-pubcom/boards/18 Guy -----Original Message----- From: wg-all-bounces(a)ogf.org [mailto:wg-all-bounces@ogf.org] On Behalf Of Greg Newby Sent: 17 January 2014 23:01 To: All WG Subject: [wg-all] New document in public comment: NSI Connection Service v2j Dear OGF Community: A new document has begun public comment. Please consider reading and providing feedback. Brief affirmations are very useful to demonstrate community input and support. More detailed analysis is, of course, welcome. All documents in public comment are accessible here: http://redmine.ogf.org/projects/editor-pubcom/boards Note that this is an updated location, using OGF's new Redmine tracker system. Anyone may register for a Redmine username. This document is newly available for public comment: * NSI Connection Service v2, Recommendation track, via NMI-WG -- Greg Newby, OGF Standards Editor Dr. Gregory Newby, Director of the Arctic Region Supercomputing Center Univ of Alaska Fairbanks-909 Koyukuk Dr-PO Box 756020-Fairbanks-AK 99775-6020 e: gbnewby(a)alaska.edu v: 907-450-8663 f: 907-450-8603 w: people.arsc.edu/~newby -- The wg-all mailing list is an umbrella list for all OGF mailing lists. If you are subscribed to any OGF mailing list, you will receive mails to wg-all. wg-all mailing list wg-all(a)ogf.org https://www.ogf.org/mailman/listinfo/wg-all

1 0

URGENT: contact of Tomohiro Kudoh
by Freek Dijkstra 18 Jan '14

18 Jan '14

Tomohiro left his laptop at the conference site. Unfortunately I do not have his phone number. If any of you do, please give him a call. I will leave the laptop at the reception of the mathematics building. Thank you! Freek

3 2

NSI Identifier format
by John MacAuley 17 Jan '14

17 Jan '14

NSI has the requirement that the networkId of a resource must be parseable from the resource identifier. This is especially true for the STP identifier as we have a specific requirement that an STP identifier need not be exposed in topology, and therefore, the network identifier must be derivable from the STP identifier if the target network is to be determined. The current URN format specification document published by the NML group for use as identifiers in NML [ref] defines the resource identifier as opaque, which also implies non-parseable. We need to resolve this issue. I have captured a proposal below for an NSI identifier that removes the opaque URN restriction and imposes structure on the URN. I hope this generates positive discussions :-) <NSI identifier> ::= <prefix> ":" <organization> ":" <type> <prefix> ::= "urn:ogf:network" <organization> ::= <string> <type> ::= <nsa> | <network> | <stp> | <sdp> | <serviceAdaptation> | <serviceDomain> | <service> <nsa> ::= "nsa:" <nsaId> <nsaId> ::= <string> <network> :: = "network:" <networkId> <networkId> ::= <string> <stp> ::= "stp:" <networkId> ":" <stpId> <stpId> ::= <localId> <label> <label> ::= “?” <labelType> “=” <labelValue> | “?”<labelType> | “” <labelType> ::= <string> <labelValue> ::= <string> <sdp> ::= "sdp:" <sdpId> <sdpId> ::= <string> /* Should this be some type of source/destination stpId combination. */ <serviceAdaptation> ::= "serviceAdaptation:" <networkId> ":" <serviceAdaptationId> <serviceAdaptationId> ::= <string> <serviceDomain> ::= "serviceDomain:" <networkId> ":" <serviceDomainId> <serviceDomainId> ::= <string> <service> ::= "service:" <networkId> ":" <serviceId> <serviceId> ::= <string>

1 0

slides presented at OGF40 Oxford
by Guy Roberts 16 Jan '14

16 Jan '14

Hello All, The slides presented at the NSI working group meetings are available to download here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6573 Guy

1 0

Delft slides
by John MacAuley 16 Jan '14

16 Jan '14

Based on the discussion today I decided to dig up these slides from Delft. They discuss some of the path finding questions Redek had today and the routing loop issue (slide 18). It specifically discusses the issue of reservation segmentation and routing. John

1 0

Delf slides
by John MacAuley 16 Jan '14

16 Jan '14

Based on the discussion today I decided to dig up these slides from Delft. They discuss some of the path finding questions Redek had today and the routing loop issue (slide 18). It specifically discusses the issue of reservation segmentation and routing. John

1 0

Issue 113 in ogf-nsi-project: Change provisionState machine to be mandatory.
by ogf-nsi-project＠googlecode.com 14 Jan '14

14 Jan '14

Status: Accepted Owner: jmacauley Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 113 by jmacauley: Change provisionState machine to be mandatory. http://code.google.com/p/ogf-nsi-project/issues/detail?id=113 Decision was made to instantiate the provisionState when the first reserve request is received for a reservation. This makes it consistent with the other state machines. However, it should be noted that a provision request cannot be received until the first version of the reservation has been successful committed. If a provision request is received before the first version of a reserve has been created, then it must be rejected with an error. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

3 4

Issue 109 in ogf-nsi-project: Align STP Label definition closer to similar types within NML.
by ogf-nsi-project＠googlecode.com 11 Jan '14

11 Jan '14

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium FoundInVersion-2.0 FixedInVersion-2.0 New issue 109 by jmacauley: Align STP Label definition closer to similar types within NML. http://code.google.com/p/ogf-nsi-project/issues/detail?id=109 The NSI STP definition was originally intended to be a generic attribute type/value pair mechanism but morphed into a Label type definition. At the moment it is too complex for the role it is performing. In addition it is not in alignment with the NML definition for LabelType. These definitions need to be normalized. Also, NML has separate definitions for LabelType (a single label) and LabelGroupType (a range of labels). Both are applicable to the STP definition and should be incorporated. For example, using an STP to specify a SONET service would require the specification of a set of timeslots associated with the service on the STP. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 3

minutes from today's NSI call...
by Guy Roberts 09 Jan '14

09 Jan '14

.... are available here: https://redmine.ogf.org/dmsf/nsi-wg?folder_id=6574 _____________________________________________________________________ Guy Roberts PhD Senior Transport Network Architect DANTE Cambridge, UK +44 1223 371316 DANTE is the project co-ordinator and operator of GÉANT, the high-speed pan-European research and education network that is transforming the way researchers collaborate. Learn more at: www.geant.net<http://www.geant.net/> Like us on: www.facebook.com/GEANTnetwork<http://www.facebook.com/GEANTnetwork> Follow us at: www.twitter.com/GEANTnews<http://www.twitter.com/GEANTnews> DANTE is the trading name of Delivery of Advanced Network Technology to Europe Limited registered in England & Wales. Registration Number 2806796. Registered Office - 9400 Garsington Road, Oxford Business Park, Oxford OX4 2HN. _____________________________________________________________________

1 0