Assuming request routing ends up defining TCP as the underlying protocol to carry request routing messages, then RFC 2385 may be a good starting point.
However, this raises the issue on protection of configuration/provisioning data (i.e key configuration data used for MD5 signature) to the CPG.
> -----Original Message-----
> From: Oliver Spatscheck [mailto:firstname.lastname@example.org]
> Sent: Friday, January 26, 2001 4:45 PM
> To: Abhi Deshmukh
> Cc: Cdn (E-mail)
> Subject: Authorized and Authenticated requests for routing and
> distributio n ??
> I think the answer has to be yes (otherwise we just ask for a crash).
> I am not sure which mechanism to choose though.
> Abhi Deshmukh writes:
> > Do requests for routing and distribution peering need to
> be authorized and
> > authenticated ? If so, what is the current thinking ?
> > - Abhi