[Nsi-wg] Issue 41 in ogf-nsi-project: Do we replace the replyTo field with a topology/NSA configuration lookup?

[John MacAuley]

Can I be so bold as to suggest we update all "FoundInVersion" to 1.Rio, and all 1.0 to 1.SC just to remove the confusion around 1.0?  Not sure if this is possible, but we could give it a try.

Thanks,
John.

On 2011-10-05, at 11:28 AM, ogf-nsi-project at googlecode.com wrote:

> Status: Accepted
> Owner: ----
> Labels: Type-Defect Priority-Medium FoundInVersion-1.0 FixedInVersion-1.1
> 
> New issue 41 by jmacau... at gmail.com: Do we replace the replyTo field with a  
> topology/NSA configuration lookup?
> http://code.google.com/p/ogf-nsi-project/issues/detail?id=41
> 
> Description of Issue:
> At the moment we get the requestor endpoint information using the replyTo  
> field in the SOAP message payload.  We are looking up the  
> csProviderEndpoint in the topology so should we also look up the requestor  
> endpoint in a similar fashion?  If we do use an external mapping mechanism  
> then which fields do we use to perform this mapping (requesterNSA)?
> 
> Discussion of Issue:
> 
> 
> Resolution of Issue:
> 
> 
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> http://www.ogf.org/mailman/listinfo/nsi-wg