Re: Should ASAP be splitted?

Qiaobing Xie <[email protected]>
Newsgroups gmane.ietf.rserpool
Message-ID <[email protected]>
Hi, Manuel,

I think you have raised a quite interesting point. But to further split
ASAP seems not a good idea, since we already see the difficult for
people to have to read two documents (ENRP and ASAP) at the same time in
order to under RSERPOOL operations. This is because they are tightly
related. Further split of ASAP will make this even harder.

We may be able to achieve the same thing you described by asking for two
separate ports for PU and PE. Just a though.

regards,
-Qiaobing

Manuel Urueña wrote:
> 
> Hi,
> 
> Reading the ASAP draft I felt that it seems a little overloaded. In
> particular, registration operations are just employed by PEs.
> 
> Maybe it would be good to put those operations in another protocol. Or
> exactly the same ASAP protocol but without PU related operations. Of
> course PE would require both protocols.
> 
> This will ease firewall protection, I mean, with ASAP firewalls should
> allow ASAP connections to both PEs and NSs. Therefore, remote PUs are
> able to send Registration operations to NSs. With two separate
> protocols, registration port could be filtered.
> 
> Has been this discussed before? comments?
> 
> Regards,
> --Manuel
> 
> --
> Manuel Uruen~a - Universidad Carlos III de Madrid
> GPG FP: 9BE9 9FFF ACFF 2887 80E6 50FE FABC A79F 5535 5A75
> 
>   ------------------------------------------------------------------------
>                        Name: signature.asc
>    signature.asc       Type: application/pgp-signature
>                 Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.