[Css-crm] Changed terms from restructuring

[John Pietras]

FYI, the concept of the protoVCDU (now Proto Transfer Frame) is/was to
allow the content of the insert zone (which is intended to be
isochronously inserted into every frame on the physical channel) to be
merged at the ground station with "proto frames" that contain everything
in a complete frame *except* the content of the Insert Zone. The Proto
Transfer Frame service is therefore *only* to be used when Insert
service is used. 

*NOTE* that insert zones may be merged into the frames further down
stream (e.g., by the MDOS), but then the Forward Coded Transfer Frame
service would be used, and the fact that the frame contains an insert
zone would be invisible to the Complex providing the Forward Coded
Transfer Frame service.

John

> -----Original Message-----
> From: css-crm-admin@mailman.ccsds.org [mailto:css-crm-
> admin@mailman.ccsds.org] On Behalf Of Takahiro Yamada
> Sent: Wednesday, November 26, 2003 4:18 AM
> To: Css-Crm@Mailman. Ccsds. Org
> Subject: Re: [Css-crm] Changed terms from restructuring
> 
> Nancy,
> 
> > 1.  C/VCDU is coded VCDU.  Is the correct replacement "coded virtual
> channel
> > frame"??
> 
> In my restructured books, Coded VCDU only appears in the TM
> Synchronization and Channel Coding Recommendation and there it is
> called "(Reed-Solomon or Turbo) Codeblock". But I think we can also
> call it "Coded Transfer Frame".
> 
> > 2. The "protect" service is what you get when Word's spell-checker
> > encounters "protoVCDU" service.  Would the replacement be protoVC
Frame
> > service?????
> 
> The concept of protoVCDU is not used in my AOS book or in the original
> AOS book, but I think we can call it proto Transfer Frame. Therefore,
> protoVCDU Service will be Proto Transfer Frame Service.
> 
> Best regards,
> Takahiro Yamada.
> 
> 
> _______________________________________________
> Css-crm mailing list
> Css-crm@mailman.ccsds.org
> http://mailman.ccsds.org/mailman/listinfo/css-crm