This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6446?nav=1&selectedTab=comments at Sun, 06 Nov 2022 08:45:08 GMT SourceForge : artf6446: DICE IDC: a network connection request protocol

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Tracker
Project: Editor     Trackers > Published > View Artifact
Artifact artf6446 : DICE IDC: a network connection request protocol
Tracker: Published
Title: DICE IDC: a network connection request protocol
Description:
This document describes a web service protocol that may be used to exchange network connection requests between network 
providers.  The protocol is the work of the DICE collaboration.
Submitted By: Guy Roberts
Submitted On: 05/17/2010 5:22 AM EDT
Last Modified: 12/13/2010 12:32 PM EST

Status / Comments Change Log Associations Attachments (2)  
Status  
Group: *
Status:* Closed
Category: * Informational
Customer: *
Priority: * 1
Assigned To: * Joel Replogle
Reported in Release: *
Fixed in Release: *
Estimated Hours: * 0
Actual Hours: * 0
resolution: * Accepted
Comments
Greg Newby: 12/13/2010 12:32 PM EST
  Action: Move
Moved from Submit OGF Draft to Published
Group changed from Infrastructure to none (no value)
resolution set to Accepted
Status changed from Ready to Publish to Closed
Joel Replogle: 12/02/2010 3:37 PM EST
  Comment:
Published as GFD.172 on 2010-11-29.   http://www.ogf.org/gf/docs
  Action: Update
Greg Newby: 10/24/2010 9:29 AM EDT
  Action: Update
Assigned To changed from Richard Hughes-Jones to Joel Replogle
Priority changed from 2 to 1
Status changed from Author Action Needed to Ready to Publish
Greg Newby: 09/03/2010 5:54 PM EDT
  Comment:
Received via email from Tom Lehman.  This is now ready for publication as GFD-I.170.

Thanks to contributors for their work on this document!
  Attachment: draft-gwdi-nsi-idcp-2010-sep-01.doc (951 KB)
  Action: Update
Added an attachment.
Greg Newby: 08/08/2010 3:56 AM EDT
  Comment:
Public comment is complete.  Please prepare a final version of the document (if needed), then let me know (tracker & email, please) when this is ready
 for final review.
  Action: Update
Assigned To changed from Joel Replogle to Richard Hughes-Jones
Priority changed from 3 to 2
Status changed from Public Comment Period to Author Action Needed
Guy Roberts: 07/30/2010 5:55 AM EDT
  Comment:
The following comments are from Remco Poortinga - van Wijnen, from SURFnet.

page 10:
-bullets #8, #10: wording suggests that Domain 2 sends events directly to Domain 1 and 3, while in fact it publishes events (as do Domains 1 and 3). 
Suggest to reword this similar to #7: '(..) publishes a CONFIRMED event(..)'.

-'1-3 These steps are optional(..)' (bottom of page):
  It is unclear from this text what determines whether path setup is triggered by message or automatically (at a specific time). Further on (section 7
.2) it becomes clear that this is determined by the 'pathSetupMode'. Suggest to make a forward reference to 7.2 to make this clearer.

page 11 (at the top):
- For the two lists (a,b,c), the c. entries are misaligned (not indented, starting at a new line).

Page 12:
The RESERVED state in the picture is referred to in the text as PENDING.
Which name is the right one?

I glimpsed over all the XML/SOAP messages (the rest of the document).
The only thing I noticed there are formatting errors (wrong font size) in 2 places:
-Page 21, start of the paragraph before the de layer2Info 'code':
  'One of the <idc:layer2info> (..)' -> 'One' font too big (12 instead of 10)

-Page 32, just above 9.1.3: Also parts in Arial 12 instead of Arial 10:
 /idc:createReservationResponse/idc:token
MAY be included, and contains a token that is to be used during path signaling. The specific use cases for tokens are the subject of ongoing research.

/idc:createReservationResponse/idc:status
MUST contain the value ACCEPTED to indicate the request was received and the parameters were valid.

Remco Poortinga - van Wijnen
SURFnet - Middleware Services (MWS)
  Action: Update
Guy Roberts: 07/29/2010 5:10 AM EDT
  Comment:
The NSI working group has proposed that this IDC protocol document become an OGF informational document to support the Network Services Interface 
protocol.  
This IDC protocol document has been prepared by the control plane group within the DICE forum.  DICE is a collaboration between various research and 
education network operators.  The group has developed the IDCP control plane protocol for use by R&E network operators to allows dynamic creation of 
international circuits.  This  protocol is publicly available and has not been published in any other forum.  For details of the DICE IDCP group and 
their work please refer to their site:
 http://www.controlplane.net/
 DICE members are active participants in the NSI working group and the NSI group has agreed that since the IDCP protocol forms an important reference 
protocol for the developing NSI standard, we would like to publish this as an OGF informational document.   We also understand that the DICE team aim 
to eventually adapt their protocol to conform to the planned NSI recommendation.
We expect that one or more additional related protocols may also be published by NSI group participants as informational documents.
The NSI working group has reviewed this document and are happy to submit it in its current form.

Guy Roberts
  Action: Update
Joel Replogle: 05/19/2010 1:15 PM EDT
  Comment:
Entered 30-day public comment on 2010-05-19.  

Comment URL is: 
http://www.ogf.org/gf/docs/comment.php?id=337
  Action: Update
Greg Newby: 05/17/2010 1:51 PM EDT
  Comment:
This document is ready for 30-day public comment.
  Action: Update
Assigned To changed from Greg Newby to Joel Replogle
Priority changed from 4 to 3
Status changed from AD Review to Public Comment Period
Guy Roberts: 05/17/2010 5:22 AM EDT
  Attachment: draft-gwdi-nsi-idcp-v1.doc (997.5 KB)
  Action: Create
Added an attachment.


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/sfmain/do/go/artf6446?nav=1&selectedTab=comments at Sun, 06 Nov 2022 08:45:08 GMT