JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY Archives

MOONSHOT-COMMUNITY Archives


MOONSHOT-COMMUNITY@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY Home

MOONSHOT-COMMUNITY  July 2011

MOONSHOT-COMMUNITY July 2011

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: [abfab] New Internet-Draft on Multihop Federations

From:

Gabriel López <[log in to unmask]>

Reply-To:

Moonshot community list <[log in to unmask]>, Gabriel López <[log in to unmask]>

Date:

Thu, 7 Jul 2011 08:55:07 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (65 lines)

Hi Sam,

El 06/07/11 22:21, Sam Hartman escribió:
>
> It plays the role of SAML metadata in our system.
ok, although it runs federation routing and topology information, and
forwards eap authentications. It plays a lot of roles :)


> However it is not required that every institution needs to deploy a trust router.
>
ok
>     Gabriel> - Does the term Trust Path refer to the AAA path/TRs path/mixed?
>
> Your AAA message goes from something near the RP to the radsec server
> near or at the IDP assuming you're actually using RADSEC.
> However other realms help set up the technical and policy trust required
> to send that message.
I can understand the AAA path in this case, but l think this mixed path
is very complicated. If every realm implements this functionality like a
AAA server it would be more interesting.
>
>     Gabriel> Section 4:
>
>     Gabriel>     - The list of security properties required by the Trust Routers
>     Gabriel> would help to a better understanding of the protocol :)
>
> * hop-by-hop integrity
> * peer entity authentication
> * for some deployments confidentiality
The last comments clarifies this point
>
> OK, let's take the example  from Margaret's draft.
> I'm going to try and enumerate all the traffic .
>
> 1) Trust routers exchange and flood routes. I don't know what the order
> of messages of this exchange is, but I'm sure people familiar with
> routing protocols do. This is amortized across all uses of the trust
> infrastructure. Messages are generated when routes change.
This is an important point that may required another important number of
exchanges, in order to build and exchange the federation topology (I'm
thinking here in something like eduroam) and to query that path by the
RP (although I suppose here only 2 messages are needed)
>
>
Have you analysed how this process (I count 18 messages for 4 realms
without routing and attribute request exchanges) could affect specific
services like SIP?
 
Thanks a lot for your comments Sam, I think this explanation (completed
with the routing part) should appear in the next version.

Best regards, Gabi.


-- 
----------------------------------------------------------------
Gabriel López Millán
Departamento de Ingeniería de la Información y las Comunicaciones
University of Murcia
Spain
Tel: +34 868888504
Fax: +34 868884151
email: [log in to unmask]

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2022
December 2021
October 2021
September 2021
August 2021
June 2021
April 2021
February 2021
January 2021
December 2020
November 2020
October 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
January 2020
November 2019
October 2019
September 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
June 2018
April 2018
November 2017
October 2017
September 2017
August 2017
July 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager