[Nsi-wg] NSI AA document ready to go to public comment

Atsuko Takefusa takefusa at nii.ac.jp
Thu Jul 7 22:13:10 EDT 2016


Hi all,

In my environment, I can see some garbage characters 
in Fig 1 and Fig 4 as I attached.
They seem to include local characters.
Could you check on them?

Thanks!

Atsuko


Atsuko Takefusa, Ph. D.
National Institute of Informatics





> 2016/07/04 18:49、Guy Roberts <Guy.Roberts at geant.org> のメール:
> 
> Hello All
>  
> Thanks Chin and John for this.  I have cleaned this up, i.e. removed comments and updated fields and dates.
>  
> This is now v7 and is available here for upload for public comment:https://redmine.ogf.org/issues/284
>  
> Guy
>  
> From: Chin Guok [mailto:chin at es.net] 
> Sent: 02 July 2016 17:41
> To: Guy Roberts
> Cc: nsi-wg at ogf.org; Greg Newby (newby at arsc.edu); Jens Jensen; Richard Hughes-Jones; Alan Sill (alan.sill at ttu.edu)
> Subject: Re: [Nsi-wg] NSI AA document ready to go to public comment
>  
> Hi all,
> 
> Both John and I made a pass to address all the outstanding comments.  We believe this is ready for final review and public comment if the clarification to the comments are satisfactory.
> 
> The updated document can be found on Redmine:
> https://redmine.ogf.org/dmsf_files/13536
> 
> Thanks!
> 
> - Chin 
> 
> Chin Guok                                                             NOC:  (510) 486-7600
> Network Engineer                                                            (800) 333-7638
> ESnet Network Engineering Group (AS293)                   
> Lawrence Berkeley National Laboratory
>  
> On Wed, Jun 29, 2016 at 4:48 AM, Guy Roberts <Guy.Roberts at geant.org> wrote:
> Hello All,
>  
> Thanks to Richard for his second review of the NSI AA document (as well as the review from Jens).  We will address the outstanding issues on today’s NSI call.
>  
> The marked up AA doc is available here:
> https://redmine.ogf.org/dmsf_files/13424
>  
> Comments by Richard:
> Most of the comments dealt with in a clear manner.
> 
> Only two points remain:
> 
> 1. How does the OE know the path and hence the Auth servers in advance of path computation?
> 
> The assumption from John:
> 
> “It is my assumption that a user community like LHCONE would use one authorization system and anyone using, or providing resource as part of, would use the same system.” May be valid but it really limits the general use of the standard.
> 
> Somewhere in maybe section 7, or the intro, you need to have some lines outlining limitation/assumption and stating that the general case if for future study.
> 
> 2. OAuth section seems to introduce new terminology.
> 
>  
> Guy
>  
>  
> Guy Roberts PhD
> Senior Transport Network Architect
> Tel: +44 (0)1223 371316 
> Mob: +44 (0)7881 336417
> Skype: guy1965
>  
> GÉANT
> Networks • Services • People 
> Learn more at www.geant.org​
>> GEANT Limited, trading as GÉANT. Registered in England & Wales. Registration Number 2806796. Registered Office – City House, 126-130 Hills Road, Cambridge CB2 1PQ
>  
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg
> 
>  
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160708/27583ec6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ????????? 2016-07-08 11.07.50.png
Type: image/png
Size: 73899 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160708/27583ec6/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ????????? 2016-07-08 11.08.07.png
Type: image/png
Size: 104317 bytes
Desc: not available
URL: <http://www.ogf.org/pipermail/nsi-wg/attachments/20160708/27583ec6/attachment-0003.png>


More information about the nsi-wg mailing list