Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: Big B, little b




One word: bUSH

Jonathan Thatcher wrote:
> 
> Rich,
> 
> I understand that we are bound by the IEEE style guide. I also understand
> that we are bound by "de law." I don't think the US Supreme Court would
> concur that the IEEE style guide has precidence over the legal system. Also,
> frankly, I'm not especially frightened by the IEEE style police. :-)
> 
> jonathan
> 
> -----Original Message-----
> From: Rich Taborek [mailto:rtaborek@earthlink.net]
> Sent: Tuesday, November 21, 2000 10:02 AM
> To: HSSG
> Subject: Re: Big B, little b
> 
> Jonathan,
> 
> Let's not mix legal issues with style issues. What we have here is a
> style issue. I can add a direct patent reference into Clause 48 for good
> measure, However, it's already in Clause 36 so it's not required. We can
> call the trasnmission code Fred or %$#@ instead of 8b/10b if we choose.
> However, neither Fred nor %$#@ comply with the IEEE Style guide.
> 
> Best Regards,
> Rich
> 
> --
> 
> Jonathan Thatcher wrote:
> >
> > Bizarre this discussion....
> >
> > Okay, so what legal rights does IBM have here and will they choose to
> > exercise them?
> >
> > jonathan
> >
> > -----Original Message-----
> > From: Ben Brown [mailto:bbrown@amcc.com]
> > Sent: Tuesday, November 21, 2000 6:21 AM
> > To: Booth Bradley
> > Cc: Shimon Muller; pat_thaler@agilent.com; bill_lane@ieee.org;
> > pbottorf@nortelnetworks.com; david_cunningham@agilent.com;
> > david_law@eur.3com.com; edward_turner@3mail.3com.com; Grow Bob;
> > jonathan.thatcher@worldwidepackets.com; justin@quaketech.com;
> > dkabal@PICOLIGHT.COM; dkesling@level1.com;
> > larry.rubin@inh-semiconductor.com; rhett@lanterncom.com;
> > rtaborek@nserial.com; shaddock@extremenetworks.com;
> > tom_alexander@pmc-sierra.com; wthirion@jatotech.com
> > Subject: Re: Big B, little b
> >
> > Brad,
> >
> > This is indeed the exact same 8B/10B using the exact same
> > encoding/decoding, disparity and data/control characters.
> > Just because we're putting a different protocol over the
> > top of this coding doesn't mean the coding isn't the same.
> >
> > Ben
> >
> > "Booth, Bradley" wrote:
> > >
> > > Okay, it's my turn... I think that it should be 8b/10b.  Not only
> because
> > > "b" stands for bit, but because the 8b/10b used by used in 10G is
> > different
> > > than the 8B/10B used in 1G.  Although our 8b/10b references the 8B/10B
> > > encoding in clause 36, we do have some different codes, and we've done
> > > things to alleviate some EMI issues.
> > >
> > > Thoughts?
> > >
> > > Cheers,
> > > Brad
> >
> > --
> > -----------------------------------------
> > Benjamin Brown
> > AMCC
> > 2 Commerce Park West
> > Suite 104
> > Bedford NH 03110
> > 603-641-9837 - Work
> > 603-491-0296 - Cell
> > 603-626-7455 - Fax
> > 603-798-4115 - Home Office
> > bbrown@amcc.com
> > -----------------------------------------
> 
> -------------------------------------------------------
> Richard Taborek Sr.                 Phone: 408-845-6102
> Chief Technology Officer             Cell: 408-832-3957
> nSerial Corporation                   Fax: 408-845-6114
> 2500-5 Augustine Dr.        mailto:rtaborek@nSerial.com
> Santa Clara, CA 95054            http://www.nSerial.com

-- 

Best Regards,
Rich
                                      
------------------------------------------------------- 
Richard Taborek Sr.                 Phone: 408-845-6102       
Chief Technology Officer             Cell: 408-832-3957
nSerial Corporation                   Fax: 408-845-6114
2500-5 Augustine Dr.        mailto:rtaborek@nSerial.com
Santa Clara, CA 95054            http://www.nSerial.com