OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-tel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [soa-tel] Up for review on Tuesdays Meeting


Title: RE: [soa-tel] Up for review on Tuesdays Meeting

Hi Mike,
 
I took a look at the use case scenarios with a view of providing these use cases but I have some comments to pass back to you and the group, to understand if I have got this correct - so here goes!

 
R3.  SOA-Tel interfaces MUST offer capability (for higher layer applications) to transparently negotiate (NAT and Firewall) perimeter traversal inbound to the enterprise.

To me this looks like we could consider use of the Parlay-X model here for QoS TS 29.199-17 as this allows various aspects of this type of requirement to be specified as name-value pairings. If this is allowed to be associated with the requested service via some form of "interface" offered to the application plane then this would meet this requirement, as the interface can issue the relevant command sequences to effect the required functionality.

R5.     Federation capabilities: communication services in one provider/enterprise realm requiring interoperation with one or more of others’ to complete a client request.

This appears to be along the lines of the SAML or WS-Trust specification but with the twist of providing a per-hop model of trust management, where I think the functionality required is a form of up-issuing or down-grading the trust between the network boundaries. This would occur where a componentized service had to cross a network boundary or boundaries to action the service request possibly initially using a repository to ask where the service resides and having to do this traversal to get to that specific component. My question is around the use of "stacked" trust data, similar to a SIP header, where the trust data between boundaries is contained in the message being transported.

Let me know what people think and I can then take a stab at the use cases for the next meeting.

Regards John

________________________________

From: Giordano, Michael (Michael) [mailto:giordano@avaya.com]
Sent: 29 May 2009 22:26
To: soa-tel@lists.oasis-open.org
Subject: [soa-tel] Up for review on Tuesdays Meeting



This is to further clarify SOA-Tel Objectives.

 

Please become prepared to comment and make additions/ changes, etc. as it will be used as a guide for what types of use cases SOA-TEL accepts in the future. 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]