Hi,
I don't think HTTP is a good candidate for the PCE application
and here are some weakness one could think of, if it used for
PCE application:
1) The HTTP is specifically designed for communications between
web server and its client, or applications in that nature.
Although it is possible to add extensions to support PCE
application, it would require a considerable amount of work.
That is not worth of the effort given the much smaller and
narrower application scope of PCE.
2) The payload of HTTP messages (both request and response)
is in form of byte stream, which is unstructured comparing
to the PCEP proposal, where the content is structured with
objects.
For the PCE application, the object based format is more
efficient in terms of processing.
3) The HTTP does not have unsolicited messages such as Notification
message and Error message that are defined by PCEP.
4) PCE architecture allows a PCE functions as a server but also as
a client communicating with another PCE server. In both cases,
the same protocol is used. PCEP supports this scenario. There
requires some work to make HTTP behavior as such.
Dean
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Adrian Farrel
>Sent: Thursday, September 29, 2005 7:27 AM
>To: [EMAIL PROTECTED]
>Subject: [Pce] Choosing the PCE protocol
>
>Hi,
>
>Three candidate protocols have been brought to my attention
>for us to consider. These are (in no specific order):
>- HTTP
>- PCECP (as draft-vasseur-pce-pcep-02.txt)
>- COPS
>
>I would like to close the nomination period, and move on to
>select our protocol.
>
>The best approach will be if supporters of the candidate
>protocols indicate (briefly) why their proposed protocol is
>suitable. It would also be helpful if they were frank about
>what the weaknesses of their proposal are.
>
>And please - this is not an election, it is an interview process.
>
>Thanks,
>Adrian
>
>PS The reason why JP is keeping quite on this is that he is an
>author of draft-vasseur-pce-pcep-02.txt and so (quite rightly)
>is not occupying the chair during this discussion.
>
>
>
>
>_______________________________________________
>Pce mailing list
>[email protected]
>https://www1.ietf.org/mailman/listinfo/pce
>
_______________________________________________
Pce mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pce
