Thanks for your reply.

While reading, I felt that adding a 'to' here make things more clearer.

As you mentioned that the existing one is correct, so its ok.

Regards,
Bharat
________________________________________
From: Jakob Heitz [[email protected]]
Sent: Wednesday, June 12, 2013 7:18 PM
To: RFC Errata System
Cc: [email protected]; [email protected]; [email protected]; 
[email protected]; [email protected]; 
[email protected]; [email protected]; Bharat Joshi; [email protected]
Subject: Re: [Editorial Errata Reported] RFC4364 (3647)

This is not necessary. The original is correct grammar.
"be" is being used in the subjunctive form.

A more modern alternative might be "If a particular host is desired to be in 
multiple virtual sites,", but the original is correct, so why bother?

--
Jakob Heitz.


On Jun 12, 2013, at 1:58 AM, "RFC Errata System" <[email protected]> 
wrote:

> The following errata report has been submitted for RFC4364,
> "BGP/MPLS IP Virtual Private Networks (VPNs)".
>
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=4364&eid=3647
>
> --------------------------------------
> Type: Editorial
> Reported by: Bharat Joshi <[email protected]>
>
> Section: 3.2
>
> Original Text
> -------------
> If it is desired to have a particular host be in multiple virtual sites, then 
> that host must determine, for each packet, which virtual site the packet is 
> associated with.
>
>
> Corrected Text
> --------------
> If it is desired to have a particular host to be in multiple virtual sites, 
> then that host must determine, for each packet, which virtual site the packet 
> is associated with.
>
> Notes
> -----
> 'host be' should be 'host to be'
>
> Instructions:
> -------------
> This errata is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party (IESG)
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC4364 (draft-ietf-l3vpn-rfc2547bis-03)
> --------------------------------------
> Title               : BGP/MPLS IP Virtual Private Networks (VPNs)
> Publication Date    : February 2006
> Author(s)           : E. Rosen, Y. Rekhter
> Category            : PROPOSED STANDARD
> Source              : Layer 3 Virtual Private Networks INT
> Area                : Internet
> Stream              : IETF
> Verifying Party     : IESG

**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely
for the use of the addressee(s). If you are not the intended recipient, please
notify the sender by e-mail and delete the original message. Further, you are 
not
to copy, disclose, or distribute this e-mail or its contents to any other 
person and
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken
every reasonable precaution to minimize this risk, but is not liable for any 
damage
you may sustain as a result of any virus in this e-mail. You should carry out 
your
own virus checks before opening the e-mail or attachment. Infosys reserves the
right to monitor and review the content of all messages sent to or from this 
e-mail
address. Messages sent to or from this e-mail address may be stored on the
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Reply via email to